Issues

Issue #10235 resolved

Wrong repository size on website after `git filter-branch` and `git push --force`

qdotdot
created an issue

I've been cleaning up a repository through rewriting the reflog and removing errorneusly addeded junk files.

After final git push --force the repository is reported online as 2.5GB while freely cloning it in results with a <400MB clone.

qdot@shadow ~/gig/wmc $ git clone git@bitbucket.org:justinhandley/webmissioncontrol.git
Cloning into 'webmissioncontrol'...
remote: Counting objects: 37737, done.
remote: Compressing objects: 100% (24655/24655), done.
remote: Total 37737 (delta 12224), reused 37737 (delta 12224)
Receiving objects: 100% (37737/37737), 382.19 MiB | 3.05 MiB/s, done.
Resolving deltas: 100% (12224/12224), done.
Checking connectivity... done.
Checking out files: 100% (34252/34252), done.

Is that another UI cache issue?

Comments (2)

  1. Erik van Zijst staff

    This is because Git does not immediately remove objects that have become orphan (your filter-branch command removed the binary files). Such objects can linger around for weeks until git-gc finally removes them from disk.

    To help you out, I have manually cleaned out the orphaned objects and your repo disk size is now down to ~386MB.

  2. Log in to comment