public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Dupont <kasperd@daimi.au.dk>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RAID-6 support in kernel?
Date: Mon, 03 Jun 2002 09:35:30 +0200	[thread overview]
Message-ID: <3CFB1C42.A03ACABC@daimi.au.dk> (raw)
In-Reply-To: <Pine.LNX.4.33.0206030044270.27651-100000@mail.pronto.tv>

Roy Sigurd Karlsbakk wrote:
> 
> hi all
> 
> I'n working on server setup with some 16 disks in RAID-5; one of them a
> spare. After a little reading, I find myself longing for support for
> RAID-6 support in kernel, giving the opportunity to allow for two failed
> drives without a chrash (see links about RAID-6 below if interested).
> 
> 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...
> 
> thanks
> 
> roy
> 
> RAID-6 layout: http://www.acnc.com/04_01_06.html

If it is supposed to survive two arbitrary disk failures something is
wrong with that figure. They store 12 logical sectors in 20 physical
sectors across 4 drives. With two lost disks there are 10 physical
sectors left from which we want to reconstruct 12 logical sectors.
That is impossible.

OTOH it is possible to construct a system with optimal capacity and
ability to survive any chosen number of disk failures. This can be
done using either a Reed-Soloman code or Lagrange interpolation of
polynomials over a finite field.

However I guess those techniques would be inefficient in software.

-- 
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razor-report@daimi.au.dk

  parent reply	other threads:[~2002-06-03  7:35 UTC|newest]

Thread overview: 23+ 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
2002-06-03  8:24   ` Roy Sigurd Karlsbakk
2002-06-03  9:25     ` Derek Vadala
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 22:27           ` Kasper Dupont
2002-06-05  9:36             ` Roy Sigurd Karlsbakk
2002-06-05  9:28           ` Roy Sigurd Karlsbakk
2002-06-05  2:51         ` jw schultz
2002-06-04 18:50   ` Bill Davidsen
2002-06-06  1:19     ` Derek Vadala
2002-06-06  8:28       ` Kasper Dupont
2002-06-03  7:35 ` Kasper Dupont [this message]
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=3CFB1C42.A03ACABC@daimi.au.dk \
    --to=kasperd@daimi.au.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.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