git clone failing, can't repack on remote
While researching this I have found a lot of messages about this concerning the exhaustion of memory, but I am not actually getting any malloc errors.
When I try and clone I get this mid-compression
error: git-upload-pack: git-pack-objects died with error. fatal: git-upload-pack: aborting due to possible repository corruption on the remote side. remote: aborting due to possible repository corruption on the remote side. fatal: early EOF fatal: index-pack failed
When I go to the remote and run
git gc it gives me this.. (same amount through compression)
error: failed to run repack
When I run
git fsck I get no output at all…
One Solution collect form web for “git clone failing, can't repack on remote”
It depends on the line you should see before
git-pack-objects died with error.
For instance, if you should see a line like:
remote: fatal: object 21f3981dd35fccd28febabd96f27241eea856c50 is corrupted
(as described in “GIT pull error – remote object is corrupted”)
In that case, you might try (on the remote server) a
git fsck --full 21f3981 ; git repack (as suggested by J-16 SDiZ)
You will find similar error message in this old (2008) thread, with Linus Torvald suggesting, for an error message like “
unable to unpack .. header“:
unable to unpack .. header” problem would at a guess be a totally
corrupted loose object. You should have a file named
and it sounds like that file is corrupt.
So far, apart from a CRLF conversion bug (that you wouldn’t have triggered on OS X anyway), I think every single time we’ve seen that, it’s been a real disk or memory