From: Vojtech Pavlik <vojtech@suse.cz>
To: Kelledin Tane <feralgod@home.com>
Cc: Volker Dierks <vd@mwi-online.de>, linux-kernel@vger.kernel.org
Subject: Re: VIA 686b Bug - once again :(
Date: Sun, 21 Oct 2001 22:49:18 +0200 [thread overview]
Message-ID: <20011021224918.A30664@suse.cz> (raw)
In-Reply-To: <200110211326.PAA01192@mail.mwi-online.de> <3BD2DCFB.C00E93B6@home.com>
In-Reply-To: <3BD2DCFB.C00E93B6@home.com>; from feralgod@home.com on Sun, Oct 21, 2001 at 09:34:35AM -0500
On Sun, Oct 21, 2001 at 09:34:35AM -0500, Kelledin Tane wrote:
> > So my questions is:
> > I'm going to buy a 3ware 6410(B)
> > IDE raid controller .. can I suspect
> > a failure safe system (in aspect to
> > the 686b problems) when all discs
> > are connected to the 3ware
> > controller?
>
> I would certainly expect so. I have a Gigabyte GA-7DX with the infamous VIA
> 686B southbridge...and an SBLive! Value...and I have no IDE devices at all
> (complete SCSI). I have never encountered data corruption.
Corruption *has* been reported on some scsi-only 686b systems, though.
> Just out of curiosity...is this IBM drive a 75GXP model? What does IBM's
> Drive Fitness Test tell you about it? I ask because the 75GXP is IMHO a
> flawed product line.
Well, I have a 30GB drive from the 75GXP family. It works just fine so far.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-10-21 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 13:26 VIA 686b Bug - once again :( Volker Dierks
2001-10-21 14:34 ` Kelledin Tane
2001-10-21 20:49 ` Vojtech Pavlik [this message]
2001-10-22 13:55 ` Krzysztof Halasa
2001-10-22 16:57 ` Rupa Schomaker
2001-10-22 17:11 ` Lorenzo Marcantonio
2001-10-21 15:05 ` Stefan Smietanowski
2001-10-21 17:37 ` Federico Sevilla III
2001-10-21 18:11 ` Alan Cox
2001-10-21 18:23 ` Stefan Smietanowski
2001-10-21 17:35 ` Federico Sevilla III
2001-10-23 8:55 ` clemens
-- strict thread matches above, loose matches on Subject: below --
2001-10-21 18:42 Federico Sevilla III
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=20011021224918.A30664@suse.cz \
--to=vojtech@suse.cz \
--cc=feralgod@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vd@mwi-online.de \
/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