From: Benjamin LaHaise <bcrl@kvack.org>
To: Cynbe ru Taren <cynbe@muq.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FYI: RAID5 unusably unstable through 2.6.14
Date: Tue, 17 Jan 2006 14:39:13 -0500 [thread overview]
Message-ID: <20060117193913.GD3714@kvack.org> (raw)
In-Reply-To: <E1EywcM-0004Oz-IE@laurel.muq.org>
On Tue, Jan 17, 2006 at 01:35:46PM -0600, Cynbe ru Taren wrote:
> In principle, RAID5 should allow construction of a
> disk-based store which is considerably MORE reliable
> than any individual drive.
>
> In my experience, at least, using Linux RAID5 results
> in a disk storage system which is considerably LESS
> reliable than the underlying drives.
That is a function of how RAID5 works. A properly configured RAID5 array
will have a spare disk to take over in case one of the members fails, as
otherwise you run a serious risk of not being able to recover any data.
> What happens repeatedly, at least in my experience over
> a variety of boxes running a variety of 2.4 and 2.6
> Linux kernel releases, is that any transient I/O problem
> results in a critical mass of RAID5 drives being marked
> 'failed', at which point there is no longer any supported
> way of retrieving the data on the RAID5 device, even
> though the underlying drives are all fine, and the underlying
> data on those drives almost certainly intact.
Underlying disks should not be experiencing transient failures. Are you
sure the problem isn't with the disk controller you're building your array
on top of? At the very least any bug report requires that information to
be able to provide even a basic analysis of what is going wrong.
Personally, I am of the opinion that RAID5 should not be used by the
vast majority of people as the failure modes it entails are far too
complex for most people to cope with.
-ben
--
"You know, I've seen some crystals do some pretty trippy shit, man."
Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-01-17 19:43 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 [this message]
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
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=20060117193913.GD3714@kvack.org \
--to=bcrl@kvack.org \
--cc=cynbe@muq.org \
--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