From: David Miller <davem@davemloft.net>
To: gitster@pobox.com
Cc: peff@peff.net, git@vger.kernel.org
Subject: Re: rogue tree objects, how to diagnose?
Date: Sat, 28 Feb 2009 22:53:32 -0800 (PST) [thread overview]
Message-ID: <20090228.225332.152995144.davem@davemloft.net> (raw)
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
> 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/
> 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.
prev parent reply other threads:[~2009-03-01 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 3:12 rogue tree objects, how to diagnose? David Miller
2009-03-01 3:20 ` Jeff King
2009-03-01 3:44 ` David Miller
2009-03-01 3:46 ` Jeff King
2009-03-01 3:58 ` David Miller
2009-03-01 5:57 ` David Miller
2009-03-01 6:40 ` Junio C Hamano
2009-03-01 6:53 ` David Miller [this message]
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=20090228.225332.152995144.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).