Repository storage still counts unreachable objects after history rewrite

[Ramin Zamani]

I rewrote a private Bitbucket Cloud repository’s history to remove 19 large historical image blobs—about 228 MB—and force-pushed the cleaned main branch. A fresh mirror of the reachable history is about 243 MB, but Bitbucket still reports roughly 665 MB and the workspace is over 800 MB.

There are no pull requests, tags, or pipelines. Could Atlassian staff trigger server-side garbage collection and remove any hidden references? Please contact me privately for the workspace and repository identifiers.

[Tomislav Tobijas]

Hi @Ramin Zamani ,

I've pinged the forum support team to take a look at this and potentially run GC on that repo/workspace. 🛎️
Someone should get back to you within 1-2 business days (usually it's quicker than that).

Cheers,
Tobi

[Viswanathan Ramachandran]

Hi @Ramin Zamani 

Welcome to the community..

This is most likely due to Bitbucket haven’t been garbage-collected yet.

Please raise a Bitbucket Support ticket and ask Atlassian to check for any remaining server-side references and run garbage collection if any.  

Atlassian Support should be able to investigate and resolve the server-side storage discrepancy.