Bitbucket storage figure doesn't make sense

[Nucleo Studio]

We have a repository that is shown to be using 960MB of storage and we are unable to commit up to it now. The thing is that on disk it totals around 9MB.

How can we "clean" this up so it really only takes up what it is?

[Ajay _view26_ · Accepted solution]

Hi @Nucleo Studio 

The 9MB you see on disk is just the current working tree.

The 960MB Bitbucket is reporting is the total size of the bare repository — that includes every commit, every version of every file, and every object in the packfile across your full history.

Large binaries that were committed at some point (images, build artifacts, datasets, etc.) stay in the Git history forever even if they've been deleted from the current branch.

[Nucleo Studio]

Ok thanks, 

I have just deleted the repository and created a new one with the same files, it now is only 6.9MB