Recovery after interrupted repack

Hannu Koivisto· Oct 26, 2011, 09:15 UTC · lore

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

Drew Northup· Nov 1, 2011, 14:49 UTC · re: Hannu Koivisto · lore

Re: Recovery after interrupted repack

On Wed, 2011-10-26 at 12:15 +0300, Hannu Koivisto wrote:

Show 11 quoted lines

> 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