From: Dylan Griffiths <dylang+kernel@thock.com>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: HPT 370 / RAID 5 possible corruption issue.]
Date: Sun, 14 Oct 2001 00:21:59 -0600 [thread overview]
Message-ID: <3BC92F07.7030801@thock.com> (raw)
In-Reply-To: <3BC381DE.4090300@thock.com> <20011012012453.C6330@unthought.net>
Jakob Østergaard wrote:
> I can't say what the current status is. But some time ago some people I know
> got burnt with silent corruption from using HPT cards with RAID5 and RAID0, the
> cards were replaced with Promise cards, and the problem went away (as it should
> - I've been running a lot of RAID on Promise cards and never saw the problem).
I've got a spare Promise card now that I will test and keep posted of the
results.
> As long as there are Promise cards to get, I'm not going anywhere near HPT.
>
> Maybe there's a fix somewhere, maybe there's a magic BIOS setting or upgrade,
> maybe something else can make it work, I don't know. Promise cards are cheap
> so I don't care.
>
> Sorry for not being able to give you "good" information, but at least now you
> got "some" information. Hope it helps, for what it's worth.
>
I wonder, if the HPT card support is so bad, or the hardware itself is so
squirelly, why it's not marked as UNSTABLE or has a note about the HW
being evil.
--
www.kuro5hin.org -- technology and culture, from the trenches.
-=-=-=-=-=-
Those that give up liberty to obtain safety deserve neither.
-- Benjamin Franklin
http://www.zdnet.com/zdnn/stories/news/0,4586,2812463,00.html
http://slashdot.org/article.pl?sid=01/09/16/1647231
-=-=-=-=-=-
prev parent reply other threads:[~2001-10-14 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 23:01 [Fwd: HPT 370 / RAID 5 possible corruption issue.] Dylan Griffiths
2001-10-11 23:24 ` Jakob Østergaard
2001-10-14 6:21 ` Dylan Griffiths [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=3BC92F07.7030801@thock.com \
--to=dylang+kernel@thock.com \
--cc=jakob@unthought.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.