Re: filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes

[Steven Cole]

On May 28, 2004, at 10:45 AM, Tomas Szepe wrote:

> On May-28 2004, Fri, 12:29 -0400
> Chris Mason <mason@xxxxxxxx> wrote:
>
> > On Fri, 2004-05-28 at 12:24, Tomas Szepe wrote:
> > > On May-28 2004, Fri, 08:46 -0400
> > > Chris Mason <mason@xxxxxxxx> wrote:
> > >
> > > > > The bottom line: I've experienced file corruption, of the following
> > > > > nature: consecutive regions (all, it seems, aligned on 256-byte
> > > > > boundaries, and typically around 1kb or 2kb in length) of seemingly
> > > > > random files are replaced by null bytes.
> > > >
> > > > The good news is that we tracked this one down recently.  2.6.7-rc1
> > > > shouldn't do this anymore.
> > >
> > > So did this only affect SMP machines?
> >
> > No, if you slept in the right spot you could hit it on UP.
>
> Uh oh.  Any idea about when the bug was introduced?

As far as I know, I was the first to publicly complain about
the bug, first to Bitmover, (I was hitting it when using bk)
who then figured out that it was a kernel bug, hence the
long "1352 NUL bytes at end of page" thread.

I first noticed the bug around April 15, doing almost nightly
kernel updates and builds.  The bug was rather hard to hit
reliably though, so it could have been there for some time
earlier.

Steven

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/