Workspace "maruen" stuck in read-only mode after reducing repository size

Hi @maruen 

The workspace you've mentioned consists of 143 repositories, and its total size is 7.1GB.

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

4. Perform cleanup operations locally to reduce the size

5. 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 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 trial period.

2. If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL: Atlassian Support  

Please let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)

Hi @maruen ,

I've pinged the forum support team to take a look at this. 👀
Someone should get back to you here in 1-2 business days.

Cheers,
Tobi

That sounds frustrating, especially after already cleaning the repository and recreating it. If the workspace usage is still showing the old storage amount, it does seem like the deleted repository data may not have been fully recalculated yet. Hopefully the support team can trigger the necessary cleanup and restore write access soon. It would also be helpful if they could confirm the current storage calculation for the workspace once the cleanup is complete.