nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

Ben

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)

All comments

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.

Ramin Zamani

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

Ben

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)

Ramin Zamani

Thank you, Ben.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud