Workspace in Read-Only Mode Due to 1 GB Limit — Assistance Required

dhiheraizen

All of a sudden today without any warning or anything, we received the message on our workspace stating:
"Your workspace has exceeded the 1 GB limit and has been placed in read-only mode."

Following this, we have:

• Moved some large repositories out of the workspace,

• Deleted several unnecessary branches and files to reduce usage.

However, we haven’t observed any change in the reported size, and the warning message still persists. The workspace remains in read-only mode, and we're unsure if cleanup actions have taken effect.

Could you please assist us in:

1. Confirming what is currently consuming space in our workspace?

2. Suggesting any additional steps we should take to resolve this?

3. Helping us restore write access once usage is under control?

Your support on this would be greatly appreciated.

Benjamin Pellaers

Hi @dhiheraizen 

The reason you're being blocked is due to changes that were announced in a blog post and via email concerning changes to the Free plan - which restricts the workspace size limit to 1GB:

• https://www.atlassian.com/blog/bitbucket/important-changes-coming-to-bitbucket-clouds-free-plan

You have two repositories in your workspace (both start with dhi) that are quite large and are the source of the bulk of the workspace size. I've just gone ahead and executed a garbage collection to attempt to reduce the size of these - but it did not reduce them much and you are still over the limit (1.1GB):

• 315.4MB > 314.6MB

• 166.4MB > 165.8MB

You have a couple of options to resolve this:

Option 1 - Delete & recreate the repositories
This is the fastest way to solve the problem, but loses metadata such as PRs, Pipelines, Permissions, etc.

1. Perform a clone of those repositories for backup purposes

2. Delete those repositories from your workspace to free up space and allow you to push. NOTE: This will permanently remove metadata such as PR's/pipelines/user permissions etc.

3. Identify the largest files in your repositories by executing the following command:

git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \| awk '/^blob/ {print substr($0,6)}' \
| sort -r --numeric-sort --key=2 \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest

3. Perform cleanup operations locally to reduce the size

4. Once complete, push those repositories back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror pushing the contents of the cleaned repository:
HTTPS
git push --mirror https://<username>@bitbucket.org/<WorkspaceID>/<RepoName>.git
SSH
git push --mirror git@bitbucket.org:<WorkspaceID>/<RepoName>.git

NOTE: This will remove metadata such as PR's/pipelines/permissions etc but will keep your commit history and binary files intact.

Option 2 - Temporarily upgrade

1. Upgrade to a paid plan and utilise our 30-day trial period to restore functionality and provide more time to reduce your repository directly without deletion. You can choose to continue or cease your trial before the end of the 30-day period.

2. If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL: 
https://support.atlassian.com/contact/ 

Please let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)