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'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.

Answer 2

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
7. Download will pause for a minute or so before it starts downloading lfs objects. Wait and it should continue.

Answer 3

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 4

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 5

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