9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Date: Mon, 21 Sep 2009 19:38:57 -0400	[thread overview]
Message-ID: <4b97c7ed935984e918f3f2f8e084cae9@quanstro.net> (raw)
In-Reply-To: <4AB7E8D7.10906@0x6a.com>

> At work, we recently had a massive failure of our RAID array.  After
> much brown noseing, I come to find that after many harddrives being
> shipped to our IT guy and him scratching his head, it was in fact the
> RAID card itself that had failed (which takes out the whole array, plus
> can take out any new drives you throw at it apparently).

i have never seen any controller fail in such a way that drives
were actually damaged.  and i would suspect serious design
issues if that is what happened.  that's like a bad ethernet
or usb controller frying your switch.

controller failure is not common for the types of controllers
i use.  for machines that are in service, controller failure
is no more common than cpu or motherboard failure.

> So I ask you all this (especially those in the 'biz): all this
> redundancy on the drive side, why no redundancy of controller cards (or
> should I say, the driver infrastructure needed)?

the high-end sas "solution" is to buy expensive dual-ported drives
and cross connect controllers and drives.  this is very complicated
and requires twice the number of ports or sas expanders.  it also
requires quite a bit of driver-level code.  it is possible
if the failure rates are low enough (and especially if cable failure
is more probable than port failure), that the extra bits and pieces
in this dual-ported setup are *less* reliable than a standard setup.
and it's all for naught if the cpu. mb or memory blow up.

i keep a cold spare controller, just in case.
(coraid sells a spares kit for the truly paranoid, like me.
and a mirroring appliance for those who are even parnoider.
of course the mirroring appliance can be mirrored, which is great
until the switch blows up.  but naturally you can use multiple
switches.  alas, no protection from meteors.)

> It is appealing to me to try and get some plan 9 supported raid card and
> have plan 9 throughout (like the coraid setup as far as I can tell), but
> this little issue bothers me.

plan 9 doesn't support any raid cards per se.  (well, maybe the wonderful
but now ancient parallel scsi drivers might.)  theoretically, intel
matrix raid supports raid and is drivable with the ahci driver.  that would
limit you to the on-board ports.  i've never tried it.  as far as i can tell,
matrix raid uses smm mode + microcode on the southbridge to operate.
(anyone know better?)  and i want as little code sneaking around behind
my back as possible.

the annoying problem with "hardware" raid is that it takes real contortions
to make an array span controllers.  and you can't recruit a hot spare from
another controller.

- erik



  reply	other threads:[~2009-09-21 23:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 16:43 erik quanstrom
2009-09-20 20:13 ` Bakul Shah
2009-09-21  3:37   ` erik quanstrom
2009-09-21 17:43     ` Bakul Shah
2009-09-21 18:02       ` erik quanstrom
2009-09-21 18:49         ` Wes Kussmaul
2009-09-21 19:21           ` erik quanstrom
2009-09-21 20:57             ` Wes Kussmaul
2009-09-21 22:42               ` erik quanstrom
2009-09-22 10:59             ` matt
2009-09-21 19:10         ` Bakul Shah
2009-09-21 20:30           ` erik quanstrom
2009-09-21 20:57             ` Jack Norton
2009-09-21 23:38               ` erik quanstrom [this message]
2009-09-21 22:07             ` Bakul Shah
2009-09-21 23:35               ` Eris Discordia
2009-09-22  0:45                 ` erik quanstrom
     [not found]               ` <6DC61E4A6EC613C81AC1688E@192.168.1.2>
2009-09-21 23:50                 ` Eris Discordia
  -- strict thread matches above, loose matches on Subject: below --
2009-09-04  0:53 Roman V Shaposhnik
2009-09-04  1:20 ` erik quanstrom
2009-09-04  9:37   ` matt
2009-09-04 14:30     ` erik quanstrom
2009-09-04 16:54     ` Roman Shaposhnik
2009-09-04 12:24   ` Eris Discordia
2009-09-04 12:41     ` erik quanstrom
2009-09-04 13:56       ` Eris Discordia
2009-09-04 14:10         ` erik quanstrom
2009-09-04 18:34           ` Eris Discordia
     [not found]       ` <48F03982350BA904DFFA266E@192.168.1.2>
2009-09-07 20:02         ` Uriel
2009-09-08 13:32           ` Eris Discordia
2009-09-04 16:52   ` Roman Shaposhnik
2009-09-04 17:27     ` erik quanstrom
2009-09-04 17:37       ` Jack Norton
2009-09-04 18:33         ` erik quanstrom
2009-09-08 16:53           ` Jack Norton
2009-09-08 17:16             ` erik quanstrom
2009-09-08 18:17               ` Jack Norton
2009-09-08 18:54                 ` erik quanstrom
2009-09-14 15:50                   ` Jack Norton
2009-09-14 17:05                     ` Russ Cox
2009-09-14 17:48                       ` Jack Norton
2009-09-04 23:25   ` James Tomaschke

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=4b97c7ed935984e918f3f2f8e084cae9@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).