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

Question

H! I installed LFS in my github repository to track my *.csv files but when someone else tried to upload other csv and I wanted to make the pull of my repository this was the result

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

My question is How can I recover the access to my repository, it doesn´t matter if I can not use anymore LFS I will move my csv files to other place, I just want to recover the access to my github repository and being able to push and pull.

Answer 1

I'll explain what I did...I tried to clone a repository from GitHub which contains GIT LFS pointers in it. I followed the following steps and got the actual files.

1. Fork the repo to one of your users
2. Go to repo settings
3. Find "Include Git LFS objects in archives" under the Archives section and check it
4. Go to the Danger Zone section, select "Archive this repository"
5. Confirm and authorize.
6. Return to the archived repository.
7. Download as .zip
8. Download will pause for a minute or so before it starts downloading lfs objects. Wait and it should continue.

Answer 2

While the error message says "This repository is over its data quota", for me the issue was not caused by the current repository. It turn out I have reached my Git LFS limit (across all repositories). So, I resolved the error by simply deleting my old Github repo which was taking a lot of LFS.

You can check if it is the case for you by going to https://github.com/settings/billing/summary and then scroll down to the Git LFS Data section. In my case, it showed me my old repo which was over the limit.

Answer 3

My repository doesn't have archives so I didn't have archive settings. This warning happened for me because I was out of Git LFS bandwidth, which you can see at https://github.com/settings/billing/summary.

This error only showed up because I was trying to push a new big file, which would use git LFS. So, I undid my git commit, deleted the file, deleted it from git lfs, and then repushed and didn't get the error anymore.

e.g.

git lfs ls-files
git reset --soft HEAD~1
git rm big_file.mp4
git lfs untrack big_file.mp4

# commit and push again

Answer 4

if its an organization, you should look here instead: https://github.com/organizations/<your_org>/settings/billing/summary

Answer 5

Can't find "Include Git LFS objects in archives" under the Archives section.

So all the previous answers are not correct. The applicable answer is as below:

• commit & push everything
• create a branch, something like fix/remove-lfs
• remove hooks git lfs uninstall
• remove lfs stuff from .gitattributes (open file, delete content - don't delete the file!)
• list all lfs files, git lfs ls-files
• run git rm --cached for each file
  • if your list is big, copy the contents into a file.txt
  • make sure you remove the number and asterik on each line, you only want the paths to the files
  • while read line; do git rm --cached "$line"; done < files.txt
• run git add for each file
  • if you have a file.txt
  • while read line; do git add "$line"; done < files.txt
• run a git status and make sure all the files were added properly
• commit everything

git add .gitattributes
git commit -m "unlfs"
git push

• check that no lfs files left with git lfs ls-files
• remove any lfs, rm -rf .git/lfs

Once your branch (fix/remove-lfs) is merged into develop, your team doesn't need to do anything other than simply pulling and checking out the new state of the world, their repository will work as-expected without git lfs installed. If git lfs is still installed, simply let them uninstall it: git lfs uninstall

Credits: Fedor, Taylor, Chase, Simon

Refer from: https://gist.github.com/everttrollip/198ed9a09bba45d2663ccac99e662201

Answer 6

1. Go to your repo settings.
2. Scroll down to the archives section.
3. Check on the checkbox of Include Git LFS objects in archives.
4. Then try to push from locally again.

Answer 7

I was able to get past this issue by only executing no. 2 and no. 3 from the previous answer. 2. Go to repo settings 3. Find "Include Git LFS objects in archives" under the Archives section and check it

I then tried to push again and succeded

Answer 8

Get a gitlab account. Use that until your account unfreezes -- maybe longer.

Answer 9

Wait for next month or you can just install your local Git server.


For Windows

[https://dl.gitea.io/gitea/1.13.0/gitea-1.13.0-windows-4.0-386.exe][1]
[https://dl.gitea.io/gitea/1.13.0/gitea-1.13.0-windows-4.0-amd64.exe][2]
[https://bonobogitserver.com/][3]    *- deploy on IIS if you do not like Apache*
[https://gitstack.com/download/][4]  *- limit developer users, not recommended* 

*For Linux -> Git lab is the best for local* 
[https://dl.gitea.io/gitea/1.13.0][5]   -  Linux and Windows version too
[docker pull store/gitlab/gitlab-ce:11.10.4-ce.0][1]   - Docker image install community edition 

https://hub.docker.com/editions/community/docker-ce-desktop-windows/ - docker for Windows

  [1]: https://dl.gitea.io/gitea/1.13.0/gitea-1.13.0-windows-4.0-386.exe
  [2]: https://dl.gitea.io/gitea/1.13.0/gitea-1.13.0-windows-4.0-amd64.exe
  [3]: https://bonobogitserver.com/
  [4]: https://gitstack.com/download/
  [5]: https://dl.gitea.io/gitea/1.13.0

Answer 10

I'd need more info to fully understand the current situation, such as the current size of the repo, how many times you've pushed, how many other colloborators are working in the same repo, but here are several possible courses of action:

1. If you don't have any collaborators (you are the only user), it's quite possible that you have a full copy of the repo locally. Are all the files intact locally?
2. Wait until next month, when you get another 1 Gb+ of free bandwidth, download the repo first thing, then change your settings.
3. It may be possible to download the latest commit as a zip file directly on the Github website if only command line access has been limited, not sure if this option is available with LFS.
4. Pay to get it unlocked
5. Check the options to see if Git-LFS can be disabled remotely (I don't think this is possible)

Once you can get the full repo cloned locally, you can turn off Git-LFS, make a commit, and either push back up to the current repo, or push up to a new repo (either at Github or a different hosting site). I'm not 100% sure if disabling Git-LFS in the config locally will also disable it fully on Github for the remote repo.