From: Junio C Hamano <gitster@pobox.com>
To: David Miller <davem@davemloft.net>
Cc: peff@peff.net, git@vger.kernel.org
Subject: Re: rogue tree objects, how to diagnose?
Date: Sat, 28 Feb 2009 22:40:34 -0800 [thread overview]
Message-ID: <7vvdqtagpp.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090228.215752.122159841.davem@davemloft.net> (David Miller's message of "Sat, 28 Feb 2009 21:57:52 -0800 (PST)")
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?
> I've put this .git dir up at:
>
> http://vger.kernel.org/~davem/netnext26_git.tar.gz
>
> if anyone wants to have a look.
>
> davem@sunset:~/src/GIT/net-next-2.6$ git fsck --full
> error: d7d82ec12e618a3152a82f7fbd459ad285403740: invalid sha1 pointer in cache-tree
> error: 95381186c4ef9d69f56bb6a9f7334ebe81dd023c: invalid sha1 pointer in cache-tree
> error: 6bea4ad565fff638d396298cb6ee7ad6a31ca252: invalid sha1 pointer in cache-tree
> error: 3c8b516f2a9634410f6c3a0ee639627d7c4a83d2: invalid sha1 pointer in cache-tree
> error: 11f0695e84bc3f83a6eea0d6fb0af2789de351ef: invalid sha1 pointer in cache-tree
> error: 7b3c81544c3117201c160af43fa983d68c614e3d: invalid sha1 pointer in cache-tree
> error: c9ee57c5c20c3b7a2d7784a4172aef8b34c3a844: invalid sha1 pointer in cache-tree
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.
next prev parent reply other threads:[~2009-03-01 6:42 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 [this message]
2009-03-01 6:53 ` David Miller
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=7vvdqtagpp.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.