Repo size: remains the same after deleting large files

[Alexgijutsu]

Hi!

I went through all the branches of two repos and deleted a good number of large files from them, but the size still remains the same. Would it possible to run garbage collection on them or double-check their size?

The size of the two repos are 1.3GB and 84.3MB.

Thanks,

Alex

[Ben · Accepted solution]

Hi @Alexgijutsu 

It is expected behaviour that the size will remain until a gc is performed on the server side. This is either performed automatically (once a certain garbage threshhold is reached) or manually by a support engineer.

I've just gone ahead and executed this manually - this has reduced your repositories as follows:

• 84MB > 33MB
• 1.3GB > 604MB

You are now well within the workspace size limit, so will not be blocked from pushing anymore.

Cheers!

- Ben (Bitbucket Cloud Support)

[Alexgijutsu]

That is awesome, thanks so much, Ben!

[Daria Kulikova_GitProtect_io]

Hello @Alexgijutsu and welcome to the Atlassian Community!

When you delete files from branches, they’re no longer referenced in your working history, but they still exist in the repository’s Git object database until garbage collection or history rewriting actually removes them. It can be the reason why the size of the repository isn't shrinking right away. 

Here is an article on this topic: https://support.atlassian.com/bitbucket-cloud/kb/repository-size-remains-the-same-after-deleting-large-files-and-running-garbage-collection-gc-on-the-remote/

Also, it's worth mentioning that before any deletion, it's better to have the data backed up, just in case you need that data for future reference. 

Regards,

Daria

[Alexgijutsu]

Thank you, Daria!