From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.49: Severe PIIX4/ATA filesystem corruption
Date: Tue, 26 Nov 2002 16:13:29 -0800 [thread overview]
Message-ID: <3DE40E29.4040408@zytor.com> (raw)
In-Reply-To: <1038357146.2658.105.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Tue, 2002-11-26 at 21:07, H. Peter Anvin wrote:
>
>>So, I finally braved it and tried running 2.5.49 on my workstation to
>>test out my RAID-6 patches. There were no patches outside the md
>>area, and the ordinary filesystems aren't on md drives.
>>
>>The two SCSI drives (SymBIOS controller) work just fine, but I have
>>gotten repeated, severe data corruption on the one ATA drive in the
>>system after only a few hours of operation.
>
>
> If you mash the innards of the page cache you'll get corruption
> everywhere, its one of the charms of testing out that area of the code
> on Linux. You might want to debug using 2.5.49 user mode linux rather
> than on raw disks. Its so much easier to use "cp" to generate a
> replacement root_fs 8)
>
Yes, that's true. However, the heavily used two SCSI disks saw no
corruption whatsoever, whereas the single, lightly used ATA disk saw
heavy corruption; if it was due to experimental unrelated code one would
have expected corruption everywhere. This does not mean that it is not
my fault (as far as UML is concerned, I tried building it quite a few
times before giving up), but given the severity of the corruption I was
seeing I thought I'd raise a red flag.
-hpa
next prev parent reply other threads:[~2002-11-27 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 21:07 H. Peter Anvin
2002-11-27 0:32 ` Alan Cox
2002-11-27 0:13 ` H. Peter Anvin [this message]
2002-11-27 1:03 ` Alan Cox
2002-11-27 0:36 ` H. Peter Anvin
2002-12-17 20:41 ` H. Peter Anvin
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=3DE40E29.4040408@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome