2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Hannu Koivisto <hidden>
Date: 2016-06-15 22:52:19
Hi, I interrupted git repack -a -f -d and now most commands say "fatal: bad object HEAD". Additionally an attempt to run git repack again says a bunch of "error: refs/heads/foo does not point to a valid object!" messages. git fsck prints a huge list of "missing blob <sha-1>" lines. I'm using a Cygwin build of git 1.7.5.1 (I also have a build of the latest master available). -- Hannu
From: Drew Northup <hidden>
Date: 2016-06-15 22:52:21
On Wed, 2011-10-26 at 12:15 +0300, Hannu Koivisto wrote:
Hi, I interrupted git repack -a -f -d and now most commands say "fatal: bad object HEAD". Additionally an attempt to run git repack again says a bunch of "error: refs/heads/foo does not point to a valid object!" messages. git fsck prints a huge list of "missing blob <sha-1>" lines. I'm using a Cygwin build of git 1.7.5.1 (I also have a build of the latest master available).
Was the result any different after running git fsck on it? If all else fails you can probably still use the contents of the reflog to fix things, but I'm not the best reference on such matters. -- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59