Request Garbage Collection

[Supun De Silva]

One of the repositories I am working on was at 3.84GB; therefore, I went ahead and removed some large files using BFG Repo-Cleaner and pushed the changes to BitBucket. Afterwards, the repository showed a size of 4.42GB on BitBucket. When searching as to why that happened, I saw some other threads saying that garbage collection might need to be run on BitBucket's side to bring down the repository size. Would it be possible to run garbage collection on the repository starting with "training-large"?

[Ben · Accepted solution]

Hi Supun,

I have executed a gc against that repository and it has reduced from 4.4GB to 592MB.

It is normal for repository sizes to inflate after using the BFG tool, as this creates dangling commits/blobs that must be targetted with a gc to remove. This will run on an automatic basis once a certain number of garbage is present, but you may also ask support at any time to execute this for you from our end manually.

Cheers!

- Ben (Bitbucket Cloud Support)

[Supun De Silva]

Thank you!

[James Howe]

@Benrather than clog up the forums with more questions, can I request the same for my team's repository "saltstack". I have attempted to remove some files from LFS, but every attempt to re-add them as regular files now results in a 0-byte file in Bitbucket, I assume because it still has the dangling hashes recorded.

[Ben]

Hi @James Howe 

I've reduced your repo from 31MB > 19MB - please check this on your end.

Cheers!

- Ben (Bitbucket Cloud Support)

[James Howe]

Thanks @Ben but that unfortunately has not solved the problem.

You will see in my latest push to it that the two .deb files still have zero size. Can you please help with ensuring they do not use LFS (I've already followed all instructions to that effect).

Or do I just have to change them so they have a different hash and hopefully they then get added as normal?

[Ben]

Hi James,

To clarify - you removed some files from LFS, but every time you try to commit them again, they keep going back to LFS - is that correct?

If so, I don't believe dangling commits are the issue here (as they were cleared by the gc).

Have you ensured that your .gitattributes file is not tracking the deb extension and therefore automatically pushing them to LFS? If this file extension is present in the file - you'll need to remove it and push the .gitattributes file back to your repo:

• https://support.atlassian.com/bitbucket-cloud/docs/use-git-lfs-with-bitbucket/

Unfortunately we can't see your repository directly without a support ticket. If you still are having issues, please let me know your timezone so I can raise one on your behalf with the appropriate support team region.

Cheers!

- Ben (Bitbucket Cloud Support)

[James Howe]

Thanks Ben. It was a bit more complicated than that, but I have now managed to solve it. Than you for your time.