linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6
Date: Mon, 11 Nov 2002 15:05:21 -0800	[thread overview]
Message-ID: <3DD037B1.8050603@zytor.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211111740060.11681-100000@filesrv1.baby-dragons.com

Mr. James W. Laferriere wrote:
> 	Hello Peter ,
> 
> On 11 Nov 2002, H. Peter Anvin wrote:
> 
>>Hi all,
>>I'm playing around with RAID-6 algorithms lately.  With RAID-6 I mean
>>a setup which needs N+2 disks for N disks worth of storage and can
>>handle any two disks failing -- this seems to be the contemporary
>>definition of RAID-6 (the originally proposed "two-dimensional parity"
>>which required N+2*sqrt(N) drives never took off for obvious reasons.)
> 
> 	Was there a discussion of the 'two-dimensional parity' on the
> 	list ?  I don't remember any (of course) .  But what other than
> 	98+2+10 ,  What was the main difficulty ?  I don't (personally)
> 	see any difficulty (other than managability/power/space) to the
> 	ammount of disks required .  Tia ,  JimL
>

No discussion of two-dimensional parity, but that was the originally
proposed RAID-6.  Noone ever productized a solution like that to the
best of my knowledge.  I don't know what you mean with "98+2+10", but
the basic problem is that with 2D parity, for N data drives you need
2*sqrt(N) redundancy drives, which for any moderate-sized RAID is a lot
(with 9 data drives you need 6 redundancy drives, so you have 67%
overhead.)  You also have the same kind of performance problems as
RAID-4 does, because the "rotating parity" trick of RAID-5 does not work
in two dimensions.  And for all of this, you're not *guaranteed* more
than dual failure recovery (although you might, probabilistically, luck
out and have more than that.)

P+Q redundancy, the current meaning of RAID-6, instead uses two
orthogonal redundancy functions so you only need two redundancy drives
regardless of how much data you have, and you can apply the RAID-5 trick
of rotating the parity around.  So from your 15 drives in the example
above, you get 13 drives worth of data instead of 9.

	-hpa




  reply	other threads:[~2002-11-11 23:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 18:52 RAID-6 H. Peter Anvin
2002-11-11 21:06 ` RAID-6 Derek Vadala
2002-11-11 22:44 ` RAID-6 Mr. James W. Laferriere
2002-11-11 23:05   ` H. Peter Anvin [this message]
2002-11-12 16:22 ` RAID-6 Jakob Oestergaard
2002-11-12 16:30   ` RAID-6 H. Peter Anvin
2002-11-12 19:01     ` RAID-6 H. Peter Anvin
2002-11-12 19:37   ` RAID-6 Neil Brown
2002-11-13  2:13     ` RAID-6 Jakob Oestergaard
2002-11-13  3:33       ` RAID-6 Neil Brown
2002-11-13 12:29         ` RAID-6 Jakob Oestergaard
2002-11-13 17:33           ` RAID-6 H. Peter Anvin
2002-11-13 18:07             ` RAID-6 Peter L. Ashford
2002-11-13 22:50             ` RAID-6 Neil Brown
2002-11-13 18:42           ` RAID-6 Peter L. Ashford
2002-11-13 22:48           ` RAID-6 Neil Brown
     [not found] <Pine.GSO.4.30.0211111138080.15590-100000@multivac.sdsc.edu>
2002-11-11 19:47 ` RAID-6 H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2005-11-13  9:05 Raid-6 Rebuild question Brad Campbell
2005-11-13 10:05 ` Neil Brown
2005-11-16 17:54   ` RAID-6 Bill Davidsen
2005-11-16 20:39     ` RAID-6 Dan Stromberg
2005-12-29 18:29       ` RAID-6 H. Peter Anvin

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=3DD037B1.8050603@zytor.com \
    --to=hpa@zytor.com \
    --cc=babydr@baby-dragons.com \
    --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).