git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Denis Bueno" <dbueno@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Recovering from repository corruption
Date: Tue, 10 Jun 2008 18:09:20 -0400	[thread overview]
Message-ID: <6dbd4d000806101509l516cf467me06fadee6ead0964@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806101431410.3101@woody.linux-foundation.org>

On Tue, Jun 10, 2008 at 17:48, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Tue, 10 Jun 2008, Denis Bueno wrote:
>> >
>> > then *if* you have the files
>> >
>> >        .git/objects/32/0bd6e82267b71dd2ca7043ea3f61dbbca16109
>> >        .git/objects/4d/0be2816d5eea5ae2b40990235e2225c1715927
>> >
>> > then those two files are interesting in themselves (most likely they are
>> > not there at all, or are zero-sized, but if you have them, please post
>> > them).
>>
>> They are attached, and they are not zero-sized.
>
> Very interesting.
>
> Both of them look fairly sane as objects (ie random - it's supposed to eb
> zlib-compressed), but both of them have the first 512 bytes *identically*
> corrupted:
>
>        0000000 6564 626e 6575 406e 6f64 6f72 6874 2e79
>                  d   e   n   b   u   e   n   @   d   o   r   o   t   h   y   .
>        0000020 6f6c 6163 2e6c 3634 0033 0000 0000 0000
>                  l   o   c   a   l   .   4   6   3  \0  \0  \0  \0  \0  \0  \0
>        0000040 0000 0000 0000 0000 0000 0000 0000 0000
>                 \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
>        *
>
> ie it's an all-zero block, except for that email-looking thing at the
> head.

Right --- that's my username and computer's hostname... for some
reason.  [You are not expected to understand this.  My computer's name
mysteriously changed.  It should not be "dorothy.local" but it is.  I
will have to find out why....]

> One thign that strikes me is that you seem to be really prone to this
> problem, since it happened to you a year ago too. I cannot swear to this,
> but I literally suspect your last case (July-2007) was the previous time
> we had a corruption issue. Why does it seem to happen to you, but not
> others?

It is the same computer on which the problem occurred last time.  It's
an OS X 10.4 macbook pro.  I haven't noticed corruption in other
places, but it's fair to assume it's occurring.  I'll have to boot off
my install disk and fsck the drive....

> Do you have some odd filesystem in play? Was the current corruption in a
> similar environment as the old one? IOW, I'm trying to find a pattern
> here, to see if there might be something we can do about it..

I can't remember if the old one happened after a panic or not, but I'd
bet it did.  The filesystem is HFS+, as indeed most OS X 10.4
installations are.  Maybe the HD has been going south?  However, that
doesn't seem likely, since when I got the computer it was new, and
that was around Jun 2007.

> But it *sounds* like the objects you lost were literally old ones, no? Ie
> the lost stuff wasn't something you had committed in the last five minutes
> or so? If so, then you really do seem to have a filesystem that corrupts
> *old* files when it crashes. That's fairly scary. What FS is it?

No, in fact I had just committed those changes not 10 minutes before
the panic.  Last time they were also fresh changes, although perhaps
older than 10 minutes.  I can't remember.


-- 
 Denis

  reply	other threads:[~2008-06-10 22:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 17:26 Recovering from repository corruption Denis Bueno
2008-06-10 17:55 ` Jakub Narebski
2008-06-10 19:38   ` Denis Bueno
2008-06-10 19:59     ` Jakub Narebski
2008-06-10 20:03       ` Denis Bueno
2008-06-10 20:14         ` Jakub Narebski
2008-06-10 20:35           ` Denis Bueno
2008-06-10 20:23         ` Linus Torvalds
2008-06-10 20:28           ` Denis Bueno
2008-06-10 21:09             ` Linus Torvalds
2008-06-10 21:22               ` Denis Bueno
2008-06-10 21:48                 ` Linus Torvalds
2008-06-10 22:09                   ` Denis Bueno [this message]
2008-06-10 22:25                     ` Tarmigan
2008-06-10 22:41                       ` Denis Bueno
2008-06-10 22:45                     ` Linus Torvalds
2008-06-10 23:00                       ` Linus Torvalds
2008-06-11  0:43                       ` Nicolas Pitre
2008-06-11  1:39                         ` Linus Torvalds
2008-06-11  1:47                           ` Nicolas Pitre
2008-06-10 21:27               ` Denis Bueno
2008-06-10 22:52               ` Junio C Hamano
2008-06-11 23:21               ` To graft or not to graft... (Re: Recovering from repository corruption) Stephen R. van den Berg
2008-06-11 23:34                 ` Jakub Narebski
2008-06-11 23:39                 ` Linus Torvalds
2008-06-12  7:14                   ` Johan Herland
2008-06-12  7:47                     ` Jeff King
2008-06-12 10:21                       ` Johan Herland
2008-06-12 12:20                         ` Stephen R. van den Berg
2008-06-10 19:40 ` Recovering from repository corruption Nicolas Pitre
2008-06-10 19:42   ` Denis Bueno

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=6dbd4d000806101509l516cf467me06fadee6ead0964@mail.gmail.com \
    --to=dbueno@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).