Community
Q&A
Bitbucket
Questions
Require gc on remote repo after using BFG Repo-Cleaner

Require gc on remote repo after using BFG Repo-Cleaner

Hi, I received a warning that my repo was well above the new 1GB limit, so I ran BFG Repo-Cleaner which reduced the local repo size from over 2GB to under 700MB.

However, upon a full push to the remote I see that the size has not reduced (in fact, it may have gone up).

It looks like a full gc needs to be run on the repo. Can somebody at Atlassian please run this for me?

Many thanks

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes

Answer accepted

Hi @tim-bbav

Often times garbage is accumulated as a result of cleanup operations - this is either removed by an automated garbage collection process (only executes once a certain threshhold is met) or via manual execution on the server-end by Atlassian staff.

I've just executed a gc which reduced the repo size from 3GB > 700MB.

Your workspace is currently consuming 989MB which is close to the 1000GB limit which will be active on 28th April. I'd suggest shrinking other repositories if possible.

Cheers!

- Ben (Bitbucket Cloud Support)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Ben

Thank you for that!

I have just shrinked the lightbox-3-installer repo and did even more shrinking on the lightbox-3 repo (having outsourced the largest files). This should have saved a couple more hundred MB. Would you mind running GC again please?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi, I'm worried that I'm going to lose write access on Monday unless I gc my repos again. They have definitely been reduced in size, but are currently showing much larger in my workspace. Can someone please help? (I wish there were a way of flagging gc without having to go through the forums)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @tim-bbav

I've just executed gc against 2 repo's that seem to have increased in size - your workspace is below 1GB again:

434MB > 97MB
896MB > 436MB

It is very important that you and your colleagues delete your local clone for those repo's and perform a fresh clone, as this will prevent pushing back old refs and inflating the size again.

Cheers!

- Ben (Bitbucket Cloud Support)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you Ben, much appreciated!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Hi @tim-bbav

Welcome to the community!

I notified the Atlassian support team here. They will reach out to you!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Was this helpful?

Thanks!

Bitbucket

DEPLOYMENT TYPE

CLOUD

PERMISSIONS LEVEL

Product Admin Site Admin

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Require gc on remote repo after using BFG Repo-Cleaner

2 answers

1 accepted

Comments for this post are closed

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PERMISSIONS LEVEL

TAGS

Atlassian Community Events