From: Phillip Susi <psusi@cfl.rr.com>
To: Michael Loftis <mloftis@wgops.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FYI: RAID5 unusably unstable through 2.6.14
Date: Tue, 17 Jan 2006 21:10:56 -0500 [thread overview]
Message-ID: <43CDA3B0.2030503@cfl.rr.com> (raw)
In-Reply-To: <7A7A0F7F294BB08D7CDA264C@d216-220-25-20.dynip.modwest.com>
Michael Loftis wrote:
> What about I said was inaccurate? I never said that it increases
> exponentially or anything like that, just that it does increase, which
> you've proven. I was speaking in the case of a RAID-5 set, where the
> minimum is 3 drives, so every additional drive increases the chance of
> a double fault condition. Now if we're including mirrors and
> stripes/etc, then that means we do have to look at the 2 spindle case,
> but the third spindle and beyond keeps increasing. If you've a 1%
> failure rate, and you have 100+ drives, chances are pretty good you're
> going to see a failure. Yes it's a LOT more complicated than that.
>
I understood you to be saying that a raid-5 was less reliable than a
single disk, which it is not. Maybe I did not read correctly. Yes, a 3
+ n disk raid-5 has a higher chance of failure than a 3 disk raid-5, but
only slightly so, and in any case, a 3 disk raid-5 is FAR more reliable
than a single drive, and only slightly less reliable than a two disk
raid-1 ( though you get 3x the space for only 50% higher cost, so 6x
cheaper cost per byte of storage ).
next prev parent reply other threads:[~2006-01-18 2:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 19:35 FYI: RAID5 unusably unstable through 2.6.14 Cynbe ru Taren
2006-01-17 19:39 ` Benjamin LaHaise
2006-01-17 20:13 ` Martin Drab
2006-01-17 23:39 ` Michael Loftis
2006-01-18 2:30 ` Martin Drab
2006-02-02 20:33 ` Bill Davidsen
2006-02-03 0:57 ` Martin Drab
2006-02-03 1:13 ` Martin Drab
2006-02-03 15:41 ` Phillip Susi
2006-02-03 16:13 ` Martin Drab
2006-02-03 16:38 ` Phillip Susi
2006-02-03 17:22 ` Roger Heflin
2006-02-03 19:38 ` Phillip Susi
2006-02-03 17:51 ` Martin Drab
2006-02-03 19:10 ` Roger Heflin
2006-02-03 19:12 ` Martin Drab
2006-02-03 19:41 ` Phillip Susi
2006-02-03 19:45 ` Martin Drab
2006-01-17 19:56 ` Kyle Moffett
2006-01-17 19:58 ` David R
2006-01-17 20:00 ` Kyle Moffett
2006-01-17 23:27 ` Michael Loftis
2006-01-18 0:12 ` Kyle Moffett
2006-01-18 11:24 ` Erik Mouw
2006-01-18 0:21 ` Phillip Susi
2006-01-18 0:29 ` Michael Loftis
2006-01-18 2:10 ` Phillip Susi [this message]
2006-01-18 3:01 ` Michael Loftis
2006-01-18 16:49 ` Krzysztof Halasa
2006-01-18 16:47 ` Krzysztof Halasa
2006-02-02 22:10 ` Bill Davidsen
2006-02-08 21:58 ` Pavel Machek
2006-01-18 10:54 ` Helge Hafting
2006-01-18 16:15 ` Mark Lord
2006-01-18 17:32 ` Alan Cox
2006-01-19 15:59 ` Mark Lord
2006-01-19 16:25 ` Alan Cox
2006-02-08 14:46 ` Alan Cox
2006-01-18 23:37 ` Neil Brown
2006-01-19 15:53 ` Mark Lord
2006-01-19 0:13 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 17:00 Salyzyn, Mark
2006-02-03 17:39 ` Martin Drab
2006-02-03 19:46 ` Phillip Susi
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=43CDA3B0.2030503@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mloftis@wgops.com \
/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