Workspace put into read only mode due to size limit

[avirajs]

Hi,

My workspace has been placed into read only mode due to size exceeding 1GB. Can you please run garbage collection to reduce the size. i can then analyze the large files in the repositories and delete them

Thanks.

Aviraj

[Syahrul]

Hi @avirajs 

Welcome to the community!

I have triggered garbage collection on the affected repository, but the size did not decrease further. This indicates that your repository contains large files that need to be removed to reduce its size.

My recommendation is to perform a bare clone of your repository and delete the large files locally. Once the repository size is reduced locally, you can delete the remote repository, create a new one, and push the local copy to the new remote. This process should help bring your workspace size below the 1 GB limit.

Please check our guide below on how to reduce your repository size:

• Reduce repository size

I hope this helps. Please let me know if you have any questions.
Regards,

Syahrul

[avirajs]

thanks for your time. Doesnt this mean that my version history will be lost? can the repo be made read-write for some duration so that i can analyze and delete large files?

It seems the .git folder is 1.3GB. Even if i delete large files, the .git folder is not going to reduce in size right? I dont see any large files though, it could be because some binary files got checked in again and again

Help me resolve this please

[Theodora Boudale]

Hi @avirajs,

Please allow me to step in as Syahrul is out of office at the moment.

Committing file deletions is not going to have any effect on the repository size, because these files will remain in the repo's history in older commits.

If your repo has any large / binary files, you can use a tool like BFG repo cleaner to rewrite history in the repo and remove these files from the history. The history of these files will indeed be lost (since you'll be removing them from the repo), but the history of the rest of the files will not be affected (only the commit hashes will change). If files are removed from history (instead of committing files deltions), then they will be removed from the .git folder.

You can check this reply of mine to a different post for more details on how to do that:

• https://community.atlassian.com/t5/Bitbucket-questions/Revert-bitbucket-repository-state-to-one-day-prior/qaq-p/1908360#M76762

After you reduce the repo's size locally, you can temporarily upgrade the repo's workspace to a paid billing plan, make use of the 30-day evaluation period in order to restore write access and push to the repo. When someone upgrades the billing plan of a workspace to the Standard or Premium plan, we offer a 30-day evaluation; if they downgrade to the Free plan before this period is over, we do not charge them. A temporary pre-authorization hold of USD 10.00 is placed on the credit card upon upgrade, but this will return to the credit card within 3 to 7 days.

The repo will likely need another git gc after you push a history rewrite; you can leave a reply here and we will run it for your repo.

Please feel free to reach out if you have any questions.

Kind regards,
Theodora