Garbage file is intermittently counted in the repository size.
When pushing to the remote repository a GC is triggered afterwards which generates a garbage file. This garbage file is cleared on the next subsequent GC.
Between those two GC's the size of the repository is displayed incorrectly within Bitbucket UI as the garbage file size is intermittently counted towards the repository total size.
- Push files to the remote
- Local repository size match the repository size of the remote.
- Repository size of the remote is larger than what is seen locally.
Workaround is to request support to run a GC or wait until the next iteration of the GC is run after a push.
If the repository size + the garbage file size is over 2GB, which is our hard limit for repository size, the repository will be set in read only state and users will not be able to push any further and will necessarily require support assistance to clear their repository size.