This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

[jac307]

Select Topic Area

Question

Body

I got this message when uploading some documents to one of my repos so I decided to upgrade my GitHub account and I am suppost to have more GB available but I am still getting this message.

This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

[esurov]

Dear @jac307 ,

The message you received indicates that your GitHub repository has exceeded its data quota, specifically in relation to Git Large File Storage (LFS). GitHub has data quotas in place to limit the amount of data you can store on their servers, and Git LFS is a way to manage large files in a Git repository.

If you've recently upgraded your GitHub account to a plan that should provide you with more storage capacity, but you're still seeing this message, there are a few things you can check and steps to take:

1. Verify Your Account: Make sure that your GitHub account is correctly upgraded and the payment has been processed successfully. You can check your account status in the GitHub settings.

2. Wait for Activation: Sometimes, it may take a little time for your upgraded account to be activated fully. Give it some time (usually a few minutes or hours), and then check if the issue is resolved.

3. Check Repository Quota: Ensure that the repository in question is associated with the upgraded account. Repository quotas are linked to the owner's account, so if the repository isn't under the upgraded account, it won't benefit from the increased storage capacity.

4. Refresh or Sync Your Repository: Sometimes, a simple refresh or sync of your repository can help update the storage information on GitHub. You can do this by pulling the latest changes to your local repository, or by clicking the "Sync" button in GitHub Desktop if you are using it.

5. Contact GitHub Support: If you've verified all of the above and the problem persists, it's a good idea to contact GitHub support. They can investigate the issue further and provide assistance.

Remember that GitHub's data quotas are subject to change, and the terms of your subscription may evolve over time. If you've upgraded your account specifically to increase your storage capacity, GitHub support should be able to help you resolve the issue if the upgrade hasn't been applied correctly to your repository.

Please note that it's essential to keep large files under control in your repositories, especially if you're using the free or lower-tier GitHub plans, as exceeding storage limits can result in restricted access to your repositories. You may also consider optimizing your use of Git LFS or storing large files in a different location if they don't need to be in the repository.

[esurov]

If you've already removed all large files from your repository and are still encountering issues related to Git LFS quotas, there are a few additional steps you can take to resolve the problem:

Check Commit History:
Make sure that there are no previous commits that still include large files. Even if you've removed the files in your latest commit, the history might still contain references to large files.

You can use the following command to check the history of large files in your repository:

git lfs ls-files

If you find any large files in the history, consider using git filter-repo or git filter-branch to rewrite the history and remove those files.

Clean Git LFS Cache:
Sometimes, Git LFS may cache files locally. Ensure that your local Git LFS cache is cleaned by running the following command:

git lfs prune

This command will remove any unreferenced files from the local LFS cache.

Update Git LFS Pointer:
Verify that the pointers in your Git LFS configuration match the actual content of your repository. You can run the following command to update pointers:

git lfs pull

This command ensures that the pointers in your working directory match the latest content.

Re-clone the Repository:
In some cases, it might be quicker to re-clone the repository after ensuring that all large files are removed. This ensures that your local copy is clean from any large files and their references.

git clone <repository-url>

Check .gitattributes:
Ensure that your .gitattributes file is correctly configured. It should only specify which files should be tracked by Git LFS. For example:

*.jpg filter=lfs diff=lfs merge=lfs -text

This line tells Git LFS to track *.jpg files.

Contact GitHub Support:
If the issue persists, it's advisable to contact GitHub support. They can investigate the specifics of your repository and account to provide targeted assistance.

Remember to always make backups before performing any history-rewriting operations, as they can be irreversible and may lead to data loss if not done carefully.

[dmtrung14]

Apparently what happened was that GitHub has recently moved to metered billing for the usage and I needed to subscribe to it. (I still get to enjoy the 1GiB/month resource, just not without entering billing info)

[Kotander]

Dear @esurov,

I have a similar problem with LFS Storage quota (my repo contains 1.7 gb of data when limits is 1 gb).

I tried almost all the methods that you suggested above and also BFG Repo-Cleaner, but since this is my first experience with GitHub repositories, I most likely did something wrong and the problem was not solved.

Now I just want to delete this large repository for to clean it up locally and upload it again. How do you think, will this help reset the quota to zero and free up space for new downloads or not? (I have already read the Github documentation on this topic, but this particular point is still not clear for me)

[esurov]

Dear Katia,

Deleting the repository and re-uploading it won't reset the LFS storage quota on GitHub. The quota is associated with your account or organization and is based on the total storage used by all repositories that use LFS within that account or organization.

To effectively address the LFS storage quota issue, you should consider the following steps:

1. Remove Large Files Locally:

   • Use tools like git-lfs and BFG Repo-Cleaner to remove large files from your local repository. This ensures that you're not pushing unnecessary files to the remote repository.

2. Push Changes:

   • After cleaning up the repository locally, push the changes to your GitHub repository. This ensures that the large files are no longer part of the history on GitHub.

3. Check Quota Status:

   • After pushing the changes, check the LFS storage quota status on the GitHub website. It may take some time for the changes to be reflected in the quota usage.

4. Adjust LFS Configuration:

   • Make sure that you have the correct .gitattributes file in your repository, specifying which files should be tracked by LFS. Verify that the patterns in the .gitattributes file match the actual file types you want to track with LFS.

5. Git LFS Pointer Cleanup:

   • Run git lfs prune to clean up any unreferenced objects.

6. Contact GitHub Support:

   • If the issue persists, and you are still exceeding the LFS storage quota, consider reaching out to GitHub support for assistance. They can provide insights into your specific account and repository situation.

Remember, deleting and re-uploading the repository won't reset the LFS storage quota. It's essential to clean up the repository, push the changes, and give some time for the changes to reflect in the storage quota usage on GitHub. If the problem persists, GitHub support can provide more tailored assistance based on your account and repository details.

[SenorCarlito1]

Dear @esurov , me and my group have been trying to create a git hub repository for Unreal and we've had similar issues but cannot seem to push anything still due to not having enough storage I received a message saying "Bandwidth: 0.0 GB / 1 GB (0%)
Storage: 1.5 GB / 1 GB (150%)" from github so I am unsure of how to free up storage