From: Vojtech Pavlik <vojtech@suse.cz>
To: Derek Vadala <derek@cynicism.com>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
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: Mon, 3 Jun 2002 11:31:28 +0200 [thread overview]
Message-ID: <20020603113128.C13204@ucw.cz> (raw)
In-Reply-To: <Pine.GSO.4.21.0206030213510.23709-100000@gecko.roadtoad.net>; from derek@cynicism.com on Mon, Jun 03, 2002 at 02:25:22AM -0700
On Mon, Jun 03, 2002 at 02:25:22AM -0700, Derek Vadala wrote:
> On Mon, 3 Jun 2002, Roy Sigurd Karlsbakk wrote:
>
> > It'll waste 9 drives, giving me a total capacity of 7n instead of 14n.
> > And, by definition, RAID-6 _can_ withstand _any_ two-drive failure.
>
> This is certainly not true.
>
> Combining N RAID-5 into a stripe wastes on N disks.
>
> If you combine two it wastes 2 disks, etc.
>
> That is, for each RAID-5 you waste a single disk worth of storage for
> partiy. I don't know what equation you're using where you get 9 drives
> from.
He was thinking "mirror", not "stripe". Mirror of 2 RAID-5 arrays (would
be probably called RAID-15 (when there is a RAID-10 for mirrored stripe
arrays)), can withstand any two disks failing anytime. Even more for
certain combinations. But it is terribly inefficient.
> As far as it's ability to withstand _any_ 2-disk failure... I'm not sure
> what you mean by definition. RAID-6 implemations don't follow a standard
> because there isn't one. Depending on how it's implemented, RAID-6 is not
> necessarily able to withstand a filaure of any two disks. We can argue as
> much as you want, but I'm not willing to invest the time.
>
> > With a 1500MHz Athlon on a typical file server where there's not much
> > writes, the CPU is sitting there chrunching RC5-64 som 99,95 % of the
> > time. I don't think it'll make much differnce with today's CPUs
>
> It's up to you to decide if the performance trade-off is worthwhile. I
> merely trying to point out that system with 2 RAID-5 is likely to incur
> the same CPU hit as a single RAID-6, implemented in the kernel.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-06-03 9:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 23:01 RAID-6 support in kernel? Roy Sigurd Karlsbakk
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 8:24 ` Roy Sigurd Karlsbakk
2002-06-03 9:25 ` Derek Vadala
2002-06-03 9:31 ` Vojtech Pavlik [this message]
2002-06-03 14:52 ` Kasper Dupont
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
2002-06-04 22:27 ` Kasper Dupont
2002-06-05 9:36 ` Roy Sigurd Karlsbakk
2002-06-05 9:36 ` Roy Sigurd Karlsbakk
2002-06-04 22:27 ` Kasper Dupont
2002-06-05 9:28 ` Roy Sigurd Karlsbakk
2002-06-04 15:49 ` Pavel Machek
2002-06-05 2:51 ` jw schultz
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-03 9:25 ` RAID-6 support in kernel? Derek Vadala
2002-06-04 18:50 ` Bill Davidsen
2002-06-06 1:19 ` Derek Vadala
2002-06-06 8:28 ` Kasper Dupont
2002-06-06 8:28 ` Kasper Dupont
2002-06-06 11:57 ` Helge Hafting
2002-06-04 18:50 ` Bill Davidsen
2002-06-03 7:35 ` Kasper Dupont
2002-06-03 8:28 ` Roy Sigurd Karlsbakk
2002-06-03 8:57 ` Kasper Dupont
2002-06-04 11:11 ` Allan Sandfeld
2002-06-04 12:51 ` Kasper Dupont
2002-06-04 13:58 ` Allan Sandfeld
2002-06-12 8:13 ` Kasper Dupont
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=20020603113128.C13204@ucw.cz \
--to=vojtech@suse.cz \
--cc=christian@konge.net \
--cc=derek@cynicism.com \
--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 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.