git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: bad object
Date: Wed, 22 Apr 2009 12:58:42 -0700	[thread overview]
Message-ID: <7vbpqo31fx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090422184842.GC9541@fieldses.org> (J. Bruce Fields's message of "Wed, 22 Apr 2009 14:48:42 -0400")

"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.

  reply	other threads:[~2009-04-22 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 18:48 bad object J. Bruce Fields
2009-04-22 19:58 ` Junio C Hamano [this message]
2009-04-22 21:00   ` J. Bruce Fields
2009-04-22 23:20     ` Nicolas Pitre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vbpqo31fx.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).