From: Andre Noll <maan@systemlinux.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Why do I need 4 disks for a raid6?
Date: Wed, 18 Mar 2009 13:18:25 +0100 [thread overview]
Message-ID: <20090318121825.GL32416@skl-net.de> (raw)
In-Reply-To: <87ljr4hsk9.fsf@frosties.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
On 20:12, Goswin von Brederlow wrote:
> I'm wondering why the kernel requires a raid6 to have at least 4
> disks (of which at most 2 can be missing). Why not 3 disks?
Yes, this limitation looks a bit arbitrary. I can not see any reason
why raid6 requires at least four disks. Probably it even works without
any significant changes if some of the checks are being relaxed.
> Now for the raid6 case. With only 1 data disk and 2 parity disks all 3
> disks should end up with identical data on them. In effect this should
> be a 3 disk raid1, a cpu intensive one.
In fact, it wouldn't be much more CPU intensive than raid5 because
the math to "calculate" the Q parity would obviously not involve any
GF multiplications at all.
> So back to my original question: Why does the kernel require 4 disks
> for a raid6 instead of allowing 3?
Dunno. Maybe Dan, Neil or HPA can tell the reason for imposing this
limitation.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-03-18 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:12 Why do I need 4 disks for a raid6? Goswin von Brederlow
2009-03-18 3:41 ` david.geib
2009-03-18 9:50 ` Goswin von Brederlow
2009-03-18 18:12 ` david.geib
2009-03-18 12:18 ` Andre Noll [this message]
[not found] ` <49C0EA5F.9070901@vshift.com>
2009-03-18 12:35 ` Andre Noll
2009-03-18 14:08 ` Goswin von Brederlow
2009-03-18 14:26 ` Robin Hill
2009-03-18 18:48 ` Goswin von Brederlow
2009-04-01 16:08 ` H. Peter Anvin
2009-04-01 17:47 ` Andre Noll
2009-04-01 20:36 ` H. Peter Anvin
2009-04-01 18:07 ` Goswin von Brederlow
2009-04-01 19:05 ` H. Peter Anvin
2009-03-19 23:35 ` Neil Brown
2009-03-20 10:20 ` Goswin von Brederlow
2009-03-23 20:20 ` Nifty Fedora Mitch
2009-03-24 19:32 ` Goswin von Brederlow
2009-04-01 16:09 ` 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=20090318121825.GL32416@skl-net.de \
--to=maan@systemlinux.org \
--cc=goswin-v-b@web.de \
--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 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.