From: Derek Vadala <derek@cynicism.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
Tedd Hansen <tedd@konge.net>, Christian Vik <christian@konge.net>,
Lars Christian Nygaard <lars@snart.com>
Subject: Re: RAID-6 support in kernel?
Date: Sun, 2 Jun 2002 17:33:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0206021721120.15478-100000@gecko.roadtoad.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0206030044270.27651-100000@mail.pronto.tv>
On Mon, 3 Jun 2002, Roy Sigurd Karlsbakk wrote:
> I am aware of that not all kernel hackers like such configurations, and
> that some will rather see small RAID-configurations connected with VLM.
> I beleive there is a reason for using RAID-6, and RAID-controller vendors
> (such as Compaq) are already using them, so why shouldn't linux do so
> also? With a high number of cheap IDE drives, the chance of one failing is
> quite high, so why not RAID-6? At least for a system doing most reads...
See the following thread from March 2002 on linux-raid:
http://groups.google.com/groups?hl=en&lr=&safe=off&th=804941541a023c63&seekm=linux.raid.Pine.LNX.4.44.0203261239110.12942-100000
You can always fake this effect by combining two 8-disk RAID-5s into a
RAID-0. It's not technically RAID-6, but can withstand a 2-disk failure,
although not _any_ 2-disk failure. However, it's my understanding that
RAID-6 cannot withstand _any_ two disk failure either (see the above
thread).
I also suspect that the use of dual RAID-5s combined with the CPU overhead
of ATA will kill most systems under any kind of load. For that matter, the
2x parity hit from RAID-6 probably wouldn't make you CPU too happy either,
even if there was a kernel driver that implemented it.
---
Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek
next prev parent reply other threads:[~2002-06-03 0:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 23:01 RAID-6 support in kernel? Roy Sigurd Karlsbakk
2002-06-03 0:33 ` Derek Vadala [this message]
2002-06-03 8:24 ` Roy Sigurd Karlsbakk
2002-06-03 9:25 ` Derek Vadala
[not found] ` <Pine.GSO.4.21.0206030213510.23709-100000@gecko.roadtoad.net>
2002-06-03 9:31 ` Vojtech Pavlik
2002-06-03 14:52 ` Kasper Dupont
2002-06-03 14:55 ` Vojtech Pavlik
2002-06-04 12:49 ` Roy Sigurd Karlsbakk
2002-06-04 15:49 ` Pavel Machek
2002-06-04 15:49 ` Pavel Machek
[not found] ` <20020604154904.J36@toy.ucw.cz>
2002-06-04 22:27 ` Kasper Dupont
2002-06-05 9:28 ` Roy Sigurd Karlsbakk
[not found] ` <3CFD3EE5.DAE3E2C9@daimi.au.dk>
2002-06-05 9:36 ` Roy Sigurd Karlsbakk
2002-06-03 17:33 ` Gregory Leblanc
2002-06-03 19:53 ` Ross Vandegrift
2002-06-04 20:20 ` Jakob Østergaard
2002-06-05 7:57 ` Luca Berra
2002-06-05 10:53 ` Jakob Østergaard
2002-06-05 19:42 ` Luca Berra
2002-06-05 21:25 ` background scanning for media defects (was Re: RAID-6 support in kernel?) Friedrich Lobenstock
2002-06-04 18:50 ` RAID-6 support in kernel? Bill Davidsen
[not found] <Pine.LNX.3.96.1020604144204.5024D-100000@gatekeeper.tmr.com>
2002-06-06 1:19 ` Derek Vadala
2002-06-06 8:28 ` Kasper Dupont
2002-06-06 11:57 ` Helge Hafting
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=Pine.GSO.4.21.0206021721120.15478-100000@gecko.roadtoad.net \
--to=derek@cynicism.com \
--cc=christian@konge.net \
--cc=lars@snart.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=tedd@konge.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).