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

Bitbucket Free workspace over 1 GB – cannot force-push cleaned 159 MB repository

csibu

Workspace youate is over the 1 GB Free workspace limit.
Repository youate-jekyll was approximately 2.8 GB.
I rewrote the repository history with git filter-repo, removing media/blog.
The cleaned repository is now 159 MiB locally.
Bitbucket is in read-only mode and rejects the force-push of the cleaned history.
Please allow/perform the repository cleanup/GC or advise how I can push the rewritten history while the workspace is read-only.

Accepted answers

All comments

Tomislav Tobijas

Hi @csibu ,

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

Ben

Hi @csibu

I have attempted to reduce the size of your repository by executing a garbage collection, but it has not reduced the size very much.

The most likely reason is due to the way metadata is stored on the server-end, PR's retain the full size of binary files in order to speed up diff calculation.

As metadata exists purely on the server-side, there's no way to target it with gc operations, and it does not exist locally (hence why there's such a large size discrepancy in local vs remote).

2.8GB > 1.5GB

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.

Perform a clone of the repository for backup purposes
Delete the repository 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.
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
Perform cleanup operations locally to reduce the size if necessary
Once complete, push the repository back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror push 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

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 depending on your preference.
If you encounter any issues during this trial/paid 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)

csibu

Thanks!

csibu

Thank you!

I upgraded temporarily, force-pushed the cleaned devel and master histories, and deleted all obsolete branches. The repository now has only master and devel, but Repository Details still shows 1.63 GB, while the cleaned local repository is 159 MiB. Could Bitbucket Support please check for retained pull-request/internal refs and run server-side garbage collection?

Ben

Hi @csibu

There are 470+ pull requests in your workspace, and even server-side garbage collection cannot target these.

The current recommendation is to delete and mirror push the repository to a blank repository, which won't include metadata and thus will result in a much smaller repository size:

https://support.atlassian.com/bitbucket-cloud/kb/how-to-duplicate-a-bitbucket-cloud-repository/

If you'd like to discuss this further with our support team - you may do so by raising a support ticket directly with us (given that you're currently on a paid trial):

https://support.atlassian.com/contact/

If you're not able to raise a support ticket, please let me know your timezone and I'll raise one on your behalf with the team who operates during your working hours.

Cheers!

- Ben (Bitbucket Cloud Support)

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