Your LFS push failed because your account is out of file storage

[dhobi]

I'm currently trying to migrate my bigger workspace repositories to GIT LFS since my workspace is getting near the 1GB usage limit. I do this by completely rewriting git history and force push. I'm on the free plan (1GB repository size / 1 GB LFS) and I'm getting this error now for my 3rd and last repository I wanted to migrate:

********************************************************************************
[ERROR] Your LFS push failed because your account is out of file storage
[ERROR] Change your plan to get more file storage for your account:
[ERROR] https://bitbucket.org/titanicvoyage/workspace/settings/plans
********************************************************************************

When I check my workspace usage though I have: 

Workspace settings: 983.7 MB of workspace storage used, 40.3 MB remaining
Git LFS: Used: 359.0 MB, Available: 665.0 MB, Total size: 1 GB

1. Why is my workspace usage still so high despite having migrated 2 of my bigger repos to GIT LFS already? Is there a "remote git gc" needed to free up some space?
2. Why can't I push to GIT LFS despite having 665 MB still available?

Thanks Daniel

[Mark C]

Hi @dhobi

Welcome to the community.

Could you provide those 2 repo names so that I can run GC?

Regards,
Mark C

[dhobi]

Hi @Mark C 

Yes, these are the 2 which should already make a difference:

https://bitbucket.org/titanicvoyage/titanicvoyagechess
https://bitbucket.org/titanicvoyage/titanicvoyagedeckplans

The 3rd repo I want to force push (after LFS migration) is this one here:
https://bitbucket.org/titanicvoyage/titanicvoyagehistoryoffline

Thanks,
Daniel

[Mark C]

Hi @dhobi

Thanks for that. I've run Git GC against those 2 repos.

For the repo "titanicvoyagechess", unfortunately, the size remains the same at 168.3 MB.

For the repo "titanicvoyagedeckplans", from 167.3 MB, it is now down to 110 KB.

Could you confirm if you've already migrated some large files for the first repo?

Regards,
Mark C

[dhobi]

Hi @Mark C 

I'm actually not sure what the problem with the titanicvoyagechess repo was. I must have missed some large files there. ¯\_(ツ)_/¯

I went ahead and replaced the whole history with a single commit. Would be great if you could run a git gc there once again (titanicvoyagechess). Thank you!

For the failed push of https://bitbucket.org/titanicvoyage/titanicvoyagehistoryoffline: I completely forgot about the fact that GIT LFS does not compress files like git does (Atlassian even has a KB about this behavior), so it's quite possible that I cannot migrate this one to LFS without hitting the 1GB LFS storage limit because it contains pretty big chat logs.

Thanks again!

Daniel