Re: rogue tree objects, how to diagnose?

From: David Miller <davem@davemloft.net>
Date: Mar 1, 2009, 06:53 UTC
Message-ID: <20090228.225332.152995144.davem@davemloft.net>
In-Reply-To: <7vvdqtagpp.fsf@gitster.siamese.dyndns.org>

From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 28 Feb 2009 22:40:34 -0800

Show 6 quoted lines

> David Miller <davem@davemloft.net> writes:
> 
> > Indeed I have some serious corruption in my pack file.
> 
> Just a sanity check; did you run verify-pack on each packfile to validate
> that suspicion?

No, sorry, I didn't validate it in that way.

I just ran verify-pack on all of the *.idx files and it produced no output.

But I do know for a fact that the corrupt tree object c9ee57c is in a pack and not sitting there explicitly under .git/objects/c9/

Show 7 quoted lines

> These may only indicate that your .git/index is corrupt but the object
> database may still be good.
> 
> We fixed an incorrect "missing object" diagnosis when your repository
> borrows objects from another repository via the alternates mechanism
> (check if .git/objects/info/alternates refers to another repository)
> fairly recently.  "Missing objects" could be false alarms.

Yes I do use alternates heavily.