From: "John Stoffel" <john@stoffel.org>
To: Maarten <maarten@ultratux.net>
Cc: Andre Noll <maan@systemlinux.org>, linux-raid@vger.kernel.org
Subject: Re: Raid6 array crashed-- 4-disk failure...(?)
Date: Fri, 19 Sep 2008 10:55:46 -0400 [thread overview]
Message-ID: <18643.48498.606058.710551@stoffel.org> (raw)
In-Reply-To: <48CFF1E9.30006@ultratux.net>
>>>>> "Maarten" == Maarten <maarten@ultratux.net> writes:
>> You could use jbod mode (or create single-disk "raid arrays") with
>> Areca or 3ware controllers and use software raid on top of that.
Maarten> True, but then that would kind of defeat the whole purpose of
Maarten> the fairly expensive card. In that case a better investment
Maarten> might be a sort of servergrade motherboard which has 6 good
Maarten> onboard controllers and at least two separate PCI buses for
Maarten> the add-on cards. (For the price of one 12 port Areca you can
Maarten> already buy a bare bones low-range server...).
Maarten> The main selling point of most hardware raid cards is that
Maarten> they seem to be doing a much better job predicting failure of
Maarten> a drive than software raid can. I don't know how they do
Maarten> that, but a fact is I've never even heard of a two-disk
Maarten> failure with hardware raid. Which of course doesn't say it
Maarten> cannot happen, but it does seem to be a lot less likely
Maarten> somehow.
Hah! I'll trump that. In a previous job we had a bunch of Netapp
Filers. Nice boxes, really nice and reliable. We had a two disk
failure in one volume, so they do happen.
Managed to get it back by swapping the disk driver controller board
between the really failed drive and the second failed drive. Took
quite a few hours of mucking about, but it was certainly better than
losing the data and doing large restores.
Nowdays Netapp has their double parity Raid6 like setup for data,
since with 1Tb disks,a second failure isn't all that unlikely.
Pretty soon I suspect disk^Wstorage will be cheap enough that we'll
just mirror and snapshot and try NOT to write to offline media if at
all possible. Except for data which hasn't been accessed recently.
HSM anyone?
John
prev parent reply other threads:[~2008-09-19 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 9:04 Raid6 array crashed-- 4-disk failure...(?) Maarten
2008-09-15 10:16 ` Neil Brown
2008-09-15 16:32 ` Maarten
2008-09-15 20:57 ` Maarten
2008-09-16 13:12 ` Andre Noll
2008-09-15 11:03 ` Peter Grandi
2008-09-15 16:57 ` Maarten
2008-09-16 19:06 ` Bill Davidsen
2008-09-15 12:59 ` Andre Noll
2008-09-15 17:14 ` Maarten
2008-09-16 8:25 ` Andre Noll
2008-09-16 17:50 ` Maarten
2008-09-16 18:12 ` Maarten
2008-09-17 8:25 ` Andre Noll
2008-09-19 14:55 ` John Stoffel [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=18643.48498.606058.710551@stoffel.org \
--to=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=maarten@ultratux.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).