On Wed, Jan 14, 2015 at 12:51:30PM +0100, Andreas Krey wrote:
> I have a repo here that is 130G, but when I clone --mirror it, the result
> is only 25G big. Because of the --mirror I don't think that I missed
> any refs that keep objects only in the source repo.
Perhaps some objects are mentioned by reflogs, but not by the refs? They
would not be transferred as part of a clone. Try:
git rev-list --objects --all | cut -d' ' -f1 | sort >reachable
git rev-list --objects --reflog | cut -d' ' -f1 | sort >reflogs
comm -13 reachable reflogs |
git cat-file --batch-check='%(objectsize:disk)' |
perl -lne '$total += $_; END { print $total }'
That should print the size, in bytes, that reflog-only objects are using
on disk. You can use "git reflog expire --expire-unreachable=now --all"
to get rid of them (and then repack).
> I already tried 'git repack -fad' and 'git gc' to shrink the original repo,
You don't need the "-f" here. Just "git repack -ad" should be enough
(and the "-f" probably makes it _way_ slower).
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
