Re: Error:non-monotonic index after failed recursive "sed" command

From: George Karpenkov <george@metaworld.ru>
Date: Jan 14, 2013, 22:57 UTC
Message-ID: <CAMoGvRKMwP_JBvNNWoN=m9AX3MP9xVgBUwxELHtry_-8Um8WKQ@mail.gmail.com>
In-Reply-To: <vpqobgrpoh7.fsf@grenoble-inp.fr>

Thanks everyone!

Progress so far:

After executing reverse sed command: find .git -name '*.*' -exec sed -i 's/ /\t/g' {} \;

And trying to switch the branch I get:

> git checkout X

error: failed to read object 51a980792f26875d00acb79a19f043420f542cfa at offset 41433013 from .git/objects/pack/pack-8d629235ee9fec9c6683d42e3edb21a1b0f6e027.pack fatal: packed object 51a980792f26875d00acb79a19f043420f542cfa (stored in .git/objects/pack/pack- 8d629235ee9fec9c6683d42e3edb21a1b0f6e027.pack) is corrupt

So the actual .pack file is corrupt, unfortunately.

On Tue, Jan 15, 2013 at 6:13 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 19 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Everybody seems to be getting an impression that .idx is the only
>> thing that got corrupt.  Where does that come from?
>
> It's the only thing that appear in the error message. This does not
> imply that it is the only corrupt thing, but gives a little hope that it
> may still be the case.
>
> Actually, I thought the "read-only" protection should have protected
> files in object/ directory, but a little testing shows that "sed -i"
> gladly accepts to modify read-only files (technically, it does not
> modify it, but creates a temporary file with the new content, and then
> renames it to the new location). So, the hope that pack files are
> uncorrupted is rather thin unfortunately.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/