From: Vojtech Pavlik <vojtech@suse.cz>
To: Ville Herva <vherva@twilight.cs.hut.fi>,
Mark Cooke <mpc@star.sr.bham.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Quick question on Software RAID support.
Date: Wed, 13 Feb 2002 22:54:49 +0100 [thread overview]
Message-ID: <20020213225449.B10409@suse.cz> (raw)
In-Reply-To: <E16axOE-0004zX-00@the-village.bc.nu> <Pine.LNX.4.44.0202131824530.29582-100000@pc24.sr.bham.ac.uk> <20020213213341.GI1105@niksula.cs.hut.fi>
In-Reply-To: <20020213213341.GI1105@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Wed, Feb 13, 2002 at 11:33:41PM +0200
On Wed, Feb 13, 2002 at 11:33:41PM +0200, Ville Herva wrote:
> On Wed, Feb 13, 2002 at 06:30:01PM +0000, you [Mark Cooke] wrote:
> > Hi Alan,
> >
> > Just a note that I have almost exactly the setup you outlined on a
> > KT7A-RAID, HPT370 onboard.
> >
> > I have a single disk on each highpoint chain, and a 3rd (parity) on
> > one of the onboard 686B channels.
> >
> > I have been seeing odd corruptions since I setup the system as RAID-5
> > though. Have you seen any reports of 686B ide corruption recently (or
> > RAID-5 for that matter) ?
> >
> > kernel 2.4.18pre6... just compiling pre9-ac3...
> > Athlon MP 1500+, mem=nopentium apm=off, NvAGP=0 in X-setup.
>
> After months of testing, we found that KT7-RAID (we tested KT7A-RAID as
> well) is basicly impossible to get working reliably. It *always* corrupted
> data from HPT370, no matter what we tried. It seemed VIA PCI problem as
> things like the pci slot of the nic, network load, nic model etc greatly
> affected corruption rate. (Via 686b ide never corrupted data, but then again
> it's integrated in the south bridge and perhaps avoids full PCI path). Our
> combination was software RAID0 (one disk on ide2 and ide3 (HPT370
> channels)).
>
> We ditched the board deep, took an Abit ST6-RAID (i815+HPT370) and have had
> no problems since.
>
> My position is that for heavy PCI load (additional IDE adapters etc), stay
> away from Via.
>
> BTW: I have a little program to stress the raid volume (or any disk device
> for that matter) that I used to trigger the corruption. It is destructive
> for the data, though. I can mail it to you, if you like.
I'd like to try that, too, so if you can send me the program ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-02-13 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:34 Mukund Ingle
2002-02-13 1:45 ` Alan Cox
2002-02-13 1:47 ` Chris Chabot
2002-02-13 4:10 ` Bill Davidsen
2002-02-13 9:24 ` Francois Romieu
2002-02-13 2:19 ` Rob Landley
2002-02-13 10:33 ` Marco Colombo
2002-02-13 11:15 ` Alan Cox
2002-02-13 14:25 ` Marco Colombo
2002-02-13 18:30 ` Mark Cooke
2002-02-13 21:33 ` Ville Herva
2002-02-13 21:54 ` Vojtech Pavlik [this message]
2002-02-13 22:12 ` Ville Herva
2002-02-15 23:48 ` Mark Cooke
2002-02-16 17:01 ` VIA KT133 (was: Re: Quick question on Software RAID support.) Ville Herva
2002-02-14 19:05 ` Quick question on Software RAID support Pavel Machek
2002-02-13 18:57 ` Thomas Schenk
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=20020213225449.B10409@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mpc@star.sr.bham.ac.uk \
--cc=vherva@twilight.cs.hut.fi \
/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®