From: Chris Mason <mason@suse.com>
To: David Madore <david.madore@ens.fr>, linux-kernel@vger.kernel.org
Subject: Re: Weird file corruption (448 bytes): FS? RAM?
Date: Tue, 21 Aug 2001 12:10:35 -0400 [thread overview]
Message-ID: <34250000.998410235@tiny> (raw)
In-Reply-To: <20010821175441.A26624@clipper.ens.fr>
In-Reply-To: <20010821175441.A26624@clipper.ens.fr>
On Tuesday, August 21, 2001 05:54:41 PM +0200 David Madore
<david.madore@ens.fr> wrote:
> Hi.
>
> This is to report an almost paranormal phenomenon :-)
>
> A few days ago I posted to this list because I had noticed a one-bit
> corruption of one of my files. This corruption was actually due to a
> defective RAM, as memtest86 showed. But memtest86 showed that only
> *one* bit was wrong. Now I am running Linux with "mem=" parameters
> that tell it not to use the page with the defective bit.
>
> Now I have just observed another file corruption. This one is more
> severe: 448 contiguous bytes were corrupted (details follow). This
> time I'm inclined to think the RAM is not to blame (448 defective
> *bytes* do not go unnoticed), but the filesystem (ReiserFS). However,
> I would like expert opinion on this. I would be grateful for any
> ideas or suggestions.
>
Hmmm, I don't know of any reiserfs bugs in 2.4.6 that look like this. You
might have found a new one, but I think it is more likely a 1 bit error in
the in-ram struct telling reiserfs which block to read in. If it reads the
wrong block, you've got big problems.
It will be hard to debug for sure until we are positive all the ram in the
box is good.
-chris
next prev parent reply other threads:[~2001-08-21 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 15:54 Weird file corruption (448 bytes): FS? RAM? David Madore
2001-08-21 16:10 ` Chris Mason [this message]
2001-08-21 18:37 ` Hans Reiser
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=34250000.998410235@tiny \
--to=mason@suse.com \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.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