From: "Kevin P. Fleming" <kpfleming@cox.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 3ware driver errors
Date: Mon, 24 Mar 2003 20:11:15 -0700 [thread overview]
Message-ID: <3E7FC8D3.7000904@cox.net> (raw)
In-Reply-To: <20030325031225.GA6851@osiris.silug.org>
Steven Pritchard wrote:
> I don't suppose you've heard if the 160GB drives are affected, have
> you? The page on support.wdc.com that someone else referred to
> specifically mentions the 200s and the 180s, but I see no mention of
> the 160s.
>
I'd like to know this too; I've got a pair of WD1600JB drives (less than
two weeks old) attached to a 3Ware 7000-2. They've been working fine so
far, but I'm not keen on finding a problem later...
next prev parent reply other threads:[~2003-03-25 3:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 21:28 3ware driver errors Steven Pritchard
2003-03-25 1:01 ` Jeff V. Merkey
2003-03-24 23:44 ` Larry McVoy
2003-03-25 0:07 ` Mark Hahn
2003-03-25 1:25 ` Jeff V. Merkey
2003-03-25 3:12 ` Steven Pritchard
2003-03-25 3:11 ` Kevin P. Fleming [this message]
2003-03-25 15:25 ` Ezra Nugroho
2003-03-25 15:26 ` Roy Sigurd Karlsbakk
2003-03-25 16:26 ` Ezra Nugroho
2003-03-27 16:02 ` ECC error in 2.5.64 + some patches Larry McVoy
2003-03-27 16:17 ` Tim Schmielau
2003-03-27 16:27 ` Larry McVoy
2003-03-27 16:39 ` Tim Schmielau
2003-03-27 16:22 ` Randy.Dunlap
2003-03-27 16:31 ` Larry McVoy
2003-03-28 0:10 ` Dave Jones
2003-03-27 16:31 ` Dave Jones
2003-03-27 17:00 ` Chris Wedgwood
2003-03-27 17:19 ` Dominik Kubla
2003-03-27 17:25 ` Chris Wedgwood
2003-04-15 4:34 ` Bill Davidsen
2003-04-15 13:24 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2003-03-24 21:44 3ware driver errors Adam Radford
2003-03-25 1:02 ` Jeff V. Merkey
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=3E7FC8D3.7000904@cox.net \
--to=kpfleming@cox.net \
--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