From: Nicolas Pitre <nico@cam.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: How to replace a single corrupt, packed object?
Date: Mon, 15 Sep 2008 12:26:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0809151223570.6279@xanadu.home> (raw)
In-Reply-To: <alpine.DEB.1.00.0809151603390.13830@pacific.mpi-cbg.de.mpi-cbg.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1399 bytes --]
On Mon, 15 Sep 2008, Johannes Schindelin wrote:
> On Sun, 10 Aug 2008, Nicolas Pitre wrote:
>
> > On Fri, 8 Aug 2008, Johannes Schindelin wrote:
> >
> > > my auto gc kicked in, and shows this:
> > >
> > > fatal: corrupt packed object for 2c1e128aa51e3a64bd61556c0cd488628b423ccf
> > > error: failed to run repack
> > >
> > > Fortunately, I have the uncorrupted object somewhere else. So I copy the
> > > single object as a loose one, and all is fine. Right?
> > >
> > > Wrong.
> >
> > Well, to be sure things are then right or wrong, just do a
> >
> > git show 2c1e128aa51e3a64bd61556c0cd488628b423ccf
> >
> > If you can't see the object before, and are able to see it once it has
> > been copied over, then things are "right".
> >
> > > Repack still picks up the corrupt object instead of the good one.
> > > What's the best way out?
> >
> > How do you repack? The only way to get rid of a corrupted object in
> > that case is to 'git repack -a -f'.
>
> Turns out I am a complete, utter moron. And I am sure René will quote me
> on that.
>
> Git would probably have taken the copied-over object, and now took the
> copied-over pack (finally!).
>
> My mistake was to keep the .keep file. And the corrupt object was -- you
> guessed it -- in the corresponding .pack file.
OK. Then I'll dig my patch out and write a test for it before
submitting it to Junio.
Nicolas
next prev parent reply other threads:[~2008-09-15 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 14:41 How to replace a single corrupt, packed object? Johannes Schindelin
2008-08-08 14:39 ` Shawn O. Pearce
2008-08-08 14:50 ` Johannes Schindelin
2008-08-08 15:21 ` Johannes Schindelin
2008-08-08 16:23 ` Shawn O. Pearce
2008-08-08 15:30 ` Pieter de Bie
2008-08-08 16:19 ` Shawn O. Pearce
[not found] ` <90E12BC7-1950-41DF-8BE5-C6B63CE060D9@ai.rug.nl>
2008-08-08 16:36 ` Shawn O. Pearce
2008-08-08 16:48 ` Johannes Schindelin
2008-08-11 2:55 ` Nicolas Pitre
2008-08-11 3:07 ` Shawn O. Pearce
2008-08-11 3:40 ` Nicolas Pitre
2008-08-11 3:46 ` Shawn O. Pearce
2008-08-11 18:59 ` Johannes Schindelin
2008-08-11 1:43 ` Nicolas Pitre
2008-09-15 14:05 ` Johannes Schindelin
2008-09-15 16:26 ` Nicolas Pitre [this message]
2008-09-15 16:34 ` Johannes Schindelin
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=alpine.LFD.1.10.0809151223570.6279@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--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).