public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Dupont <kasperd@daimi.au.dk>
To: Allan Sandfeld <linux@sneulv.dk>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RAID-6 support in kernel?
Date: Wed, 12 Jun 2002 10:13:53 +0200	[thread overview]
Message-ID: <3D0702C1.81C1E350@daimi.au.dk> (raw)
In-Reply-To: <Pine.LNX.4.33.0206031025400.30424-100000@mail.pronto.tv> <200206041311.03631.linux@sneulv.dk> <3CFCB7D1.5A09615E@daimi.au.dk> <200206041558.12209.linux@sneulv.dk>

Allan Sandfeld wrote:
> 
> I just looked at it. It is possible allright and the diagram looks ok.
> 
> If you have 3 disks A,B and C the parity is calculated by dividing the diskw
> into typical lines, in this example I use 3 like they use on the diagram. We
> then have a parity per line and one per disk. You can only regenerate one
> block per parity, but since you have two full independ parities you can
> replace any two.
> 
>   A1 B1 C1 P1 (P1 = A1^B1^C1)
>   A2 B2 C2 P2
>   A3 B3 C3 P3
>   PA PB PC
>  (PA=A1^A2^A3)
> 
> As you can see if you wish to chech the parity for one read line(eg.A1-C1),
> you can check directly against the horizontal parity P1. But if you wish to
> check the horizontal parity you need to read the entire diskarray!

I don't think I got that one. How many disks would you use, and
how would you distribute the above fields across the disks? If
you put each column on a disk you can handle any two lost
blocks, but not two lost disks. Or would you use a total of 15
disks? Or do you have some way of placing them on 5 disks with
3 blocks on each disk?

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

      reply	other threads:[~2002-06-12  8:13 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
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 [this message]

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=3D0702C1.81C1E350@daimi.au.dk \
    --to=kasperd@daimi.au.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@sneulv.dk \
    /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