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; } } }

Unable to push cleaned repo – workspace in read-only mode even after reducing repo size with BFG

BrijeshJaiswal

Hi Bitbucket Community,

I’m facing an issue where my Bitbucket Cloud workspace has been locked in read-only mode because it exceeded the 1 GB limit.

To resolve this, I cloned the repo with `--mirror`, used BFG to strip large files over 100MB, ran aggressive GC, and reduced my local repo size significantly.

However, when I try to push the cleaned mirror back to Bitbucket, I still get this error:

Thank you in advance!

Accepted answers

All comments

Theodora Boudale

Hi @BrijeshJaiswal and welcome to the community!

Your workspace has access to multiple workspaces. I can trigger a garbage collection for the remote repos, this may help bring the total workspace storage down. I don't know if it will be enough to bring the workspace's storage below 1 GB, but it's something we can try. If you'd like me to do that, please let me know the last two letters of the workspace ID. You can find the workspace ID in the URL on your browser. For example, if the URL of the repo is https://bitbucket.org/workspace-id/repo/src/master/, then workspace-id in the URL is the ID of the workspace. Please also keep in mind that I can only trigger the garbage collection for repos that your account has access to.

Kind regards,
Theodora

BrijeshJaiswal

Hi Atlassian team,
Thanks for your help so far!

Please trigger a garbage collection for my Bitbucket workspace.

- Workspace ID: (last two letters: "in")
- Repository: <redacted>

Thanks again!
— Brijesh Jaiswal

Theodora Boudale

Hi,

Thank you for the details. Just a heads up, I removed the repo name from your post to protect your privacy.

I ran a git gc on the repo. Its size has been reduced but it's still larger than the limit, it's at 2.3 GB.

Next steps:

The workspace admin/owner can temporarily upgrade the billing plan of the workspace to a paid one, so that write access is restored. You will then be able to push your changes. We provide a 30-day evaluation for the Standard and Premium plan and we only charge at the end of this period. If the admin downgrades to the Free plan before the 30-day evaluation period is over, we won't charge them.
This workspace has other repos that you don't have access to, and those contribute to the workspace storage. Reducing the size only of this repo you posted about, will not be enough to bring the total workspace storage down to less than 1 GB. Action will need to be taken for the other large repos in the workspace that you don't have access to.

Kind regards,
Theodora

BrijeshJaiswal

Hi,

Thank you so much for your support in reducing the repo size! Really appreciate your help

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