Dear Bitbucket Support/Community,
I am writing to request guidance on safely reclaiming LFS storage space across all repositories in our workspace.
Our Situation:
We currently have approximately 3.7 TB of Git LFS data consumed. Our account stopped functioning correctly two days ago, likely due to exceeding storage limits.
Our Goal:
We need to drastically reduce our LFS usage. We do not need to retain any of the large historical binary files; however, we must keep the repositories themselves functional (maintenance of commit history, text-based source code, and branches is essential).
Questions:
Safe Cleanup Procedure: What is the recommended, safe method to remove LFS objects from the server storage for all repositories? We understand git lfs prune cleans local files, but we need to ensure the server storage is freed.
"Is there a method to bulk delete these files? Due to the high volume (approximately 100,000 files), deleting them manually via the UI would take an impractical amount of time."
Local Cleanup: How can we enforce this cleanup on local developer machines to ensure the large files don't accidentally get pushed back?
Account Status: Our LFS usage has been high (around 3.7 TB) for some time, but the account only stopped working/locked out two days ago. Was there a specific policy update, grace period expiration, or billing trigger that caused this enforcement to kick in now?
We appreciate any advice or documentation you can provide to help us resolve this quickly.
Thank you.
Welcome to the community.
I checked your workspace on our end.
It appears that the workspace plan was downgraded to the Free plan due to payment problem, that is why you're getting blocked because the workspace has 17 users while the Free plan's limit is only 5.
I'd highly recommend sorting out the workspace plan payment first you make any changes with your LFS storage.
Let me know how it goes.
Regards,
Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.