From: Derek Vadala <derek@cynicism.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: Re: RAID-6 support in kernel?
Date: Wed, 5 Jun 2002 18:19:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0206051716530.16571-100000@gecko.roadtoad.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1020604144204.5024D-100000@gatekeeper.tmr.com>
On Tue, 4 Jun 2002, Bill Davidsen wrote:
> On Sun, 2 Jun 2002, Derek Vadala wrote:
>
> > 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.
>
> I think (hope) you meant 1+5, which will stand any three disk failure, and
> up to 1+N/2 if just the right drives fail. They never do, of course.
I did mean RAID-0 combined with RAID-5. You can search for RAID-50 for
more info. The configuration you describe (RAID-5s combined into a mirror)
would have a disk overhead that is worse than RAID-10/RAID-0+1. For two
5-disk RAID-5s combined into a RAID-1 you end up using six of your disks
for parity and disk mirroring:
RAID-1 --------> RAID-5 (D0,D1,D2,D3,P0)
|--> RAID-5 (D0,D1,D2,D3,P0)
(four disks used for data, only one from each RAID-5 can fail)
With RAID-10:
RAID-0 --------> RAID-1 (D0,D0)
|--> RAID-1 (D1,D1)
|--> RAID-1 (D2,D2)
|--> RAID-1 (D3,D3)
|--> RAID-1 (D4,D4)
(five disks used for data, one from each mirror can fail)
With RAID-50:
RAID-0 --------> RAID-5 (D0,D2,D4,D6,P0)
|--> RAID-5 (D1,D3,D5,D7,P0)
(two disks wasted only one from each RAID-5 can fail)
I believe that I/O performance would be similar for each
configuration. I'll try to run some tests in the next few days.
> I doubt it. Unless you run a system with heavy CPU demand there are lots
> of cycles for this stuff. I run 0+1 several places and I don't see serious
> CPU load. I would be very interested in RAID-6 in the kernel, but I have
Mirroing doesnt hit the CPU nearly as much as RAID-5 does. I suspect
RAID-6 would incur greater overhead because of its double parity blocks.
But, there's no point in arguing about kernel RAID-6 without data to back
it up.
---
Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek
next parent reply other threads:[~2002-06-06 1:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.1020604144204.5024D-100000@gatekeeper.tmr.com>
2002-06-06 1:19 ` Derek Vadala [this message]
2002-06-06 8:28 ` RAID-6 support in kernel? Kasper Dupont
2002-06-06 11:57 ` Helge Hafting
2002-06-02 23:01 Roy Sigurd Karlsbakk
2002-06-03 0:33 ` Derek Vadala
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-04 18:50 ` Bill Davidsen
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.0206051716530.16571-100000@gecko.roadtoad.net \
--to=derek@cynicism.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).