From: Bill Davidsen <davidsen@tmr.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: "Callahan, Tom" <CallahanT@tessco.com>,
'Andargor The Wise' <andargor@yahoo.com>,
linux-raid@vger.kernel.org
Subject: Re: First RAID Setup
Date: Thu, 22 Dec 2005 09:20:22 -0500 [thread overview]
Message-ID: <43AAB626.3060708@tmr.com> (raw)
In-Reply-To: <43A1D642.2010301@wasp.net.au>
Brad Campbell wrote:
> Callahan, Tom wrote:
>
>> It is always wise to build in a spare however, that being said about all
>> raid levels. In your configuration, if a disk fails in your RAID5, your
>> array will go down. RAID5 is usually 3+ disks, with a mirror. So you
>> should
>> have 3 disks at minimum, and then a 4th as a spare.
>>
>
> /me wonders in the days of reliable RAID-6 why we use RAID-5 + spare?
>
> RAID-6 has saved me twice now from dual drive failures on a 15 disk
> array.
> It's schweeeeeeeeeett
It's also a lot more overhead... RAID-5 needs to update just one parity
block beyond the data written. As I understand the Q sum in RAID-6, and
watching disk access rates, each write requires the entire stripe to be
read, then P and Q calculated, then written. You can do the P with a
read+write, but since you have to read the entire stripe for Q, you save
a read by recalculating the P from data.
Did I say that right, Neil?
If you are seeing dual drive failures, I suspect your hardware has
problems. We run multiple 3 and 6 TB databases, and over a dozen 1 TB
data caching servers, all using a lot of small fast disk, and I haven't
seen a real dual drive failure in about 8 years.
We did see some cases which looked like dual failures, it turned out to
be a firmware limitation, controller not waiting for the bus to settle
after a real failure, and thinking the next i/o had failed (or similar,
in any case a false fail on the transaction after the real fail). If you
run two PATA drives on the same cable in master/slave, it's at least
possible that this could happen with consumer grade hardware as well.
Just a thought, dual failures are VERY unlikely unless one triggers the
other in some way, like failing the bus or cabinet power supply.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2005-12-22 14:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 20:02 First RAID Setup Callahan, Tom
2005-12-15 20:22 ` Andargor The Wise
2005-12-15 20:46 ` Brad Campbell
2005-12-15 21:31 ` Tobias Hofmann
2005-12-16 1:51 ` Max Waterman
2005-12-16 8:01 ` Tobias Hofmann
2005-12-16 1:53 ` Neil Brown
2005-12-16 8:08 ` Tobias Hofmann
2005-12-19 1:02 ` Neil Brown
2005-12-19 9:03 ` Max Waterman
2005-12-16 8:42 ` Gordon Henderson
2005-12-22 14:20 ` Bill Davidsen [this message]
2005-12-22 14:24 ` Mattias Wadenstein
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 17:03 Andrew Burgess
2005-12-15 21:46 Callahan, Tom
2005-12-15 20:37 Callahan, Tom
2005-12-17 0:00 ` Andargor The Wise
2005-12-17 2:01 ` Andargor The Wise
2005-12-18 22:08 ` Andargor The Wise
2005-12-22 14:27 ` Bill Davidsen
2005-12-22 15:00 ` Andargor The Wise
2005-12-15 19:35 Callahan, Tom
2005-12-15 19:44 ` Andargor The Wise
2005-12-22 14:00 ` Bill Davidsen
2005-12-15 19:09 Andargor The Wise
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=43AAB626.3060708@tmr.com \
--to=davidsen@tmr.com \
--cc=CallahanT@tessco.com \
--cc=andargor@yahoo.com \
--cc=brad@wasp.net.au \
--cc=linux-raid@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.