Re: rogue tree objects, how to diagnose?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

> David Miller <davem@xxxxxxxxxxxxx> 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/

> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux