git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: bad object

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2009, 19:58 UTC
Message-ID
<7vbpqo31fx.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090422184842.GC9541@fieldses.org>
"J. Bruce Fields" <bfields@fieldses.org> writes:
Show 10 quoted lines
> 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.

Show 6 quoted lines
>
> 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.
Previous: J. Bruce FieldsNext: J. Bruce Fields
Message 2 of 4 in “bad object”
  1. J. Bruce FieldsApr 22, 2009
  2. Junio C HamanoApr 22, 2009
  3. J. Bruce FieldsApr 22, 2009
  4. Nicolas PitreApr 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.