Community
Q&A
Bitbucket
Questions
Repository storage still counts unreachable objects after history rewrite

Repository storage still counts unreachable objects after history rewrite

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.

3 answers

1 accepted

2 votes

Answer accepted

Hi @Ramin Zamani

Bitbucket Cloud does have an automated gc process, but this only runs once a certain garbage threshhold is met.

I've triggered it manually from my side - this has reduced the repo size down to 243MB.

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you, Ben.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks, Tobi. I appreciate you escalating this. I’ll wait for the support team to investigate and confirm whether garbage collection can be run.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Tomislav Tobijas likes this

0 votes

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Suggest an answer

Was this helpful?

Thanks!

Bitbucket

DEPLOYMENT TYPE

CLOUD

PERMISSIONS LEVEL

Product Admin

We're moving! The community forums are migrating to a new platform on September 22. Learn more

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Repository storage still counts unreachable objects after history rewrite

3 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PERMISSIONS LEVEL

TAGS

Atlassian Community Events