Hi, our workspace innohive has been placed in read-only mode after exceeding the 1GB workspace storage limit, and we're now unable to push anything at all — including an attempt to revert the change that caused it.
What happened:
- We were blocked from pushing due to Git LFS storage being full (1GB Free-plan limit; ~13.44GB actually in use via historical pay-as-you-go storage additions under the legacy "Bitbucket 2017 Free" billing line — those additions appear to have stopped working recently).
- To reduce usage, we ran
git filter-repo locally to strip ~2,419 orphaned LFS pointer objects (~9.5GB, verified unreferenced by any current branch) and force-pushed the rewritten history to our fit-fit repo (26 branches/tags). - Workspace storage jumped from ~735MB to ~1.3GB instead of shrinking — the old objects are apparently still counted until server-side GC runs, and the newly-pushed pack (~509MB) added on top.
- The workspace then went read-only for exceeding 1GB.
- We tried pushing the original pre-rewrite history back to undo it, but that was rejected too — every push, either direction, is now blocked.
What we need: someone from Atlassian to run garbage collection on the fit-fit repository to prune the now-unreachable objects (we're not part of a paid workspace so we can't file a ticket directly). We have the exact pre-rewrite commit SHA for every branch if it's useful for a revert-then-GC approach instead.
This is blocking every push for our whole team, not just this one repo, so any pointer to someone who can help would be appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.