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

  • Does using msysgit lead to repository corruption?
  • Go back in history to an undamaged version?
  • Jar file gets corrupted after pushing to github
  • fatal: git-write-tree: error building trees
  • git fsck reporting “sha1 mismatch”
  • Git recovery: “object file is empty”. How to recreate trees?
  • 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…

    ideas?

  • Checkout Jenkins Pipeline Git SCM with credentials?
  • Should I delete unused branches?
  • Does gitignore support regexp
  • calling cryptdb from eclipse java project
  • What exact rules does git / diff exactly follow to determine conflcts?
  • git cherry-pick: output resulting new commit sha
  • 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“:

    The “unable to unpack .. header” problem would at a guess be a totally
    corrupted loose object. You should have a file named

    .git/objects/b2/8b949a1a3c8eb37ca6eefd024508fa8b253429
    

    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
    corruption.

    Git Baby is a git and github fan, let's start git clone.