From: Pat <finnegpt@purdue.edu>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, David Madore <david.madore@ens.fr>
Subject: Re: filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes
Date: Fri, 28 May 2004 11:42:54 -0500 [thread overview]
Message-ID: <200405281142.54299.finnegpt@purdue.edu> (raw)
In-Reply-To: <1085761753.22636.3329.camel@watt.suse.com>
On Friday 28 May 2004 11:29, Chris Mason wrote:
> On Fri, 2004-05-28 at 12:24, Tomas Szepe wrote:
> > On May-28 2004, Fri, 08:46 -0400
> >
> > Chris Mason <mason@suse.com> 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.
I saw this once when using 2.6.6, it was messing up the filesystem
structures as well (ext2 & ext3), replacing mostly with nulls, some
with random letters and numbers, for 4-6 character lengths, and not on
any nice boundaries. Since I stopped trying to use the ATI framebuffer
driver (this is on a 21164A alpha, 164LX motherboard, ATI Mach64 CT
video), it seems to have stopped. Also, I noticed that the framebuffer
driver didn't work so well.
2.6.7-rc1 seems to have a compile error for alpha as well, I'll post
that in a separate email.
Pat
--
PLUG Vice President -- http://plug.purdue.org
The Computer Refuge -- http://computer-refuge.org
Purdue University Research Computing -- http://www.itap.purdue.edu/rcs
next prev parent reply other threads:[~2004-05-28 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 12:28 filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes David Madore
2004-05-28 12:46 ` Chris Mason
2004-05-28 13:05 ` Lenar Lõhmus
2004-05-28 16:24 ` Tomas Szepe
2004-05-28 16:29 ` Chris Mason
2004-05-28 16:42 ` Pat [this message]
2004-05-28 16:54 ` Chris Mason
2004-05-28 16:45 ` Tomas Szepe
2004-05-28 16:55 ` Chris Mason
2004-05-28 16:58 ` Steven Cole
2004-05-29 11:56 ` Lenar Lõhmus
[not found] ` <1085750828.1914.385.camel@tribesman.namesys.com>
[not found] ` <1085751695.22636.3163.camel@watt.suse.com>
2004-05-31 16:48 ` I would like to see ReiserFS V3 enter a feature freeze real soon Hans Reiser
2004-06-01 11:37 ` Chris Mason
2004-06-01 17:02 ` Hans Reiser
2004-06-01 18:53 ` Chris Mason
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=200405281142.54299.finnegpt@purdue.edu \
--to=finnegpt@purdue.edu \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
/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.