From: "Tomi Orava" <tomimo+linux-kernel@ncircle.nullnet.fi>
To: linux-kernel@vger.kernel.org
Cc: "Ying-Hung Chen" <ying@yingternet.com>
Subject: Re: wierd raid 1 problem
Date: Wed, 10 Sep 2003 21:59:35 +0300 (EEST) [thread overview]
Message-ID: <39807.192.168.9.10.1063220375.squirrel@ncircle.nullnet.fi> (raw)
In-Reply-To: <1063140808.30962.0.camel@dhcp23.swansea.linux.org.uk>
> 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
I actually saw the same thing happen to me a week ago with
linux-2.4.23-pre1+xfs (xfs bk).
The really wierd thing was that I copied several big files from one
disk-array to another and ran md5sum before & after the copy. The files
were instact before copying, but failed right after the copy. When I
started investigating what the hell is wrong, the next md5sum on the
destination filesystem was succesfull ... and that was it (no more errors).
The source filesystem was two disk RAID1 array with XFS (Sil680).
The destination filesystem was RAID1+0 four disk array with XFS as well
(HPT374 with hightech binary driver 1.10, as 2.4.22 still doesn't work at
all with Epox 8K9A3+ motherboard's integrated HPT374 with dma).
I ran the latest memtest86 for 24h (29 passes) without any errors.
Regards,
Tomi Orava
prev parent reply other threads:[~2003-09-10 19:01 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
2003-09-10 18:59 ` Tomi Orava [this message]
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=39807.192.168.9.10.1063220375.squirrel@ncircle.nullnet.fi \
--to=tomimo+linux-kernel@ncircle.nullnet.fi \
--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
Powered by JetHome