All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Aveling <bena.001@optusnet.com.au>
To: Jeff King <peff@peff.net>
Cc: Edward Thomson <ethomson@edwardthomson.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] fsck: do not canonicalize modes in trees we are checking
Date: Sun, 19 Oct 2014 23:40:22 +1100	[thread overview]
Message-ID: <5443B136.4060009@optusnet.com.au> (raw)
In-Reply-To: <20141016002021.GA27509@peff.net>

On 16/10/14 11:20, Jeff King wrote:
> On Thu, Oct 16, 2014 at 10:46:19AM +1100, Ben Aveling wrote:
>
> I have a corrupt repository, and every time I run fsck, it
> reports one corrupt object, then stops.
> Corrupt how? Bit-corruption, or a malformed object?

Bit-corruption, in multiple places.

> If you have a non-corrupted version of the repository, the simplest 
> thing is to just pack it, copy the resulting packfile to the broken 
> repository (again, using "cp" or "rsync" and not git), and then repack 
> there. 

This seems to have worked. I also had to move away the existing .idx and 
copy in a new one before it was happy.

I'm not sure that what I've done is so different from simply copying the 
other version of the repository - there shouldn't have been anything in 
the corrupt version that wasn't also in the good one. But any rate, it 
worked.

Thanks, Ben

  reply	other threads:[~2014-10-19 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 15:47 [RFC/PATCH] fsck: do not canonicalize modes in trees we are checking Jeff King
2014-09-23 16:23 ` Edward Thomson
2014-09-23 16:30   ` Jeff King
2014-10-12 22:37     ` Ben Aveling
2014-10-14  8:21       ` Jeff King
     [not found]         ` <543F074B.2050907@optusnet.com.au>
2014-10-16  0:20           ` Jeff King
2014-10-19 12:40             ` Ben Aveling [this message]
2014-10-20  9:21               ` Jeff King

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=5443B136.4060009@optusnet.com.au \
    --to=bena.001@optusnet.com.au \
    --cc=ethomson@edwardthomson.com \
    --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.