From: Chuck Ebbert <76306.1226@compuserve.com>
To: Bernd Eckenfels <ecki-news2004-05@lina.inka.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: deadlock with 2.6.9
Date: Fri, 12 Nov 2004 22:45:13 -0500 [thread overview]
Message-ID: <200411122248_MC3-1-8E97-BFE6@compuserve.com> (raw)
On Sun, 07 Nov 2004 at 09:22:14 +0100 Bernd Eckenfels wrote:
> > Get a real RAID controller (3Ware, not some crappy pseudo-RAID junk.) They are
> > much more reliable than software RAID.
>
> On what sample do you base this claim?
>
> Generally hardware raid sooner or later makes problems (especially if you
> run raid5 in degenerate mode or try to rebuild by disk replacing with
> differen/old signature). Also bus hangs are commonly not very well received
> by hw raid firmware or drivers.
I had 28 mirror sets on Compaq SMART2/p controllers in one server (four
controllers, two SCSI channels each, seven disks per channel.) All the disks
on channel A of each controller were mirrored to those on channel B, so even
complete failure of one channel didn't cause a problem.
Once a disk was marked 'failed' in the controller NVRAM there was no way to
convince it that some newly-inserted disk contained valid data.
Booting up with SCSI cables connected wrongly (channels A and B swapped) got you
a nice error message informing you of this fact. Swapping SCSI IDs on different
disks on the same channel was also detected and reported nicely.
And attempting to boot with a bad cable (bent pin) gave a message saying 'either
power down NOW and check cables or I will mark every disk on that channel as
failed.'
Of course this system was 100% Compaq; even the disks had Compaq firmware
though the labels said IBM. And it was very expensive...
--Chuck Ebbert 12-Nov-04 22:42:32
next reply other threads:[~2004-11-13 3:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 3:45 Chuck Ebbert [this message]
2004-11-15 20:23 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 1:11 Chuck Ebbert
2004-11-07 5:55 Chuck Ebbert
2004-11-07 7:49 ` Chris Stromsoe
2004-11-07 7:53 ` Chris Stromsoe
2004-11-07 8:22 ` Bernd Eckenfels
2004-11-02 7:03 Chris Stromsoe
2004-11-04 17:01 ` Chris Stromsoe
2004-11-06 22:36 ` Chris Stromsoe
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=200411122248_MC3-1-8E97-BFE6@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ecki-news2004-05@lina.inka.de \
--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
all inboxes | Powered by JetHome®