trigger the GC

[nunomira]

My repository tells me that it's out of space.

Can you help me trigger the GC, please?

Thanks!

[Ben · Accepted solution]

Hi @nunomira ,I have attempted to reduce the size of your largest repositories by executing a garbage collection, but it has not reduced the size much (likely because you are storing large binary files), and your workspace is still 1.2GB:

• 324.8MB > 324.2MB

• 212.5MB > 210MB

• 152.8MB > 152.8MB

• 112.0MB > 111.5MB

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
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 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: Atlassian Support  

Please let me know how this goes.

Cheers!

- Ben (Bitbucket Cloud Support)

[nunomira]

Hi @Ben ,

Thank you so much for your help!

The strange thing is that it tells me that I have 648 MB remaining now.
This is because I had deleted a repository.
But even after this, I wasn't able to perform a push.

And the problem persists... I get an error regarding taking space over 1GB.
Can you help me?

Thanks!

[nunomira]

@Ben It says 648 MB remaining

[Ben]

Hi @nunomira 

You have access to a few workspaces. The one you've shared in the screenshot is one of three workspaces tied to your account (the workspaceID starts with an L) - this workspace is indeed 341mb.

The workspace I'm referring to that you are not able to push to (starts with N) is tied to your user account. This is the workspace that must be reduced. 

You can view a list of the workspaces you have access to by clicking your avatar in the top-right corner, then selecting All Workspaces and checking each of these.

Cheers!

- Ben (Bitbucket Cloud Support)

[Rishabh Jhawar]

Hi @nunomira

Welcome to the community!

Community members don’t have access to run GC on your repo. Please see Ben’s (Atlassian Team) response in this thread—I believe it will be helpful in your case.

If you still need additional support , I will request assistance from the Atlassian Support team.

Regards,

Rishabh