From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ying-Hung Chen <ying@yingternet.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: wierd raid 1 problem
Date: Tue, 09 Sep 2003 21:53:29 +0100 [thread overview]
Message-ID: <1063140808.30962.0.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <3F5E14FC.5090001@yingternet.com>
On Maw, 2003-09-09 at 18:59, Ying-Hung Chen wrote:
> the corrupted files seem to 'recover' itself if i leave the machine
> alone for a while or umount and mount back the filesystem.
>
> does anyone have this type of temperory file corruption problem? I
> tested it against 2.4.2x kernel including the last vanilla 2.4.22 + xfs
> patches, they all seem to have the same problem
Classic symptoms of bad memory or a kernel bug corrupting data. See if
the box passes memtest86 as a starter
next prev parent reply other threads:[~2003-09-09 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 17:59 Ying-Hung Chen
2003-09-09 20:53 ` Alan Cox [this message]
2003-09-10 18:59 ` Tomi Orava
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=1063140808.30962.0.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ying@yingternet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®