From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 22 Apr 2009 19:58:42 GMT
Subject: Re: bad object
Message-ID: <7vbpqo31fx.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20090422184842.GC9541@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> writes:

> Just today operations started warning:
>
> 	error: Could not read 4e69489a0ac11a9b62a25923975bfc370a30eae5
>
> This is Documentation/networking/baycom.txt from
> 518e6540831c69422faecceee8f964bd439ac9d0 (pre-2.6.13), which is easy
> enough to find from another repository and fix the problem.
>
> But I'm curious--how do I find out what pack file that object should be
> in, and what the corruption looks like?

The former you should be able to read from either "verify-pack -v" or
"show-index" output.  After finding the offset for the object data in the
pack, a bit of "dd seek=" would be needed to extract the data.

>
> This is the third time I've found corruption in a repository on this
> laptop, so I'm a little suspicious of the hardware.  (The second time I
> reported here: http://marc.info/?l=git&m=121968278319668&w=2.)
>
> --b.