From: Alex <creamyfish@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Is this enough for us to have triple-parity RAID?
Date: Fri, 20 Apr 2012 10:27:08 +0800 [thread overview]
Message-ID: <CAMqP1GVjqBMTiM9Yb+PxQLULWDnG8x3uvzuLFKya3NXsTPt_hg@mail.gmail.com> (raw)
In-Reply-To: <4F905690.3060301@zytor.com>
I think when David says 'generator', he doesn't mean the generator of the order
8 Galois field, he means an arbitrary set of number in it which can render the
system of equations solvable to up to a certain number of data
disks(not necessarily
255). He uses a brute-force method with the help of a Python program to actually
figure that out. It looks pretty cool to me since I have known the
system of 4 equations
generally fails to render a solution for a while, but now I know
exactly how many ways
it may fail...
Cheers,
Alex
On Fri, Apr 20, 2012 at 2:16 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 04/17/2012 01:18 PM, David Brown wrote:
>>
>> For quad parity, we can try g3 = 8 as the obvious next choice in the
>> pattern. Unfortunately, we start hitting conflicts. To recover missing
>> data, we have to solve multiple simultaneous equations over G(2⁸), whose
>> coefficients depend on the index numbers of the missing disks. With
>> parity generators (1, 2, 4, 8), some of these combinations of missing
>> disk indexes lead to insoluble equations when you have more that 21 disks.
>>
>
> That is because 255 = 3*5*17... this means {02}^3 = {08} is not a generator.
>
> -hpa
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-20 2:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 6:11 Is this enough for us to have triple-parity RAID? Alex
2012-04-17 7:58 ` David Brown
2012-04-17 16:37 ` Stefan /*St0fF*/ Hübner
2012-04-18 14:15 ` Alex
2012-04-18 14:11 ` David Brown
2012-04-17 17:16 ` Piergiorgio Sartor
2012-04-17 20:18 ` David Brown
2012-04-17 20:54 ` Piergiorgio Sartor
2012-04-18 18:22 ` Piergiorgio Sartor
2012-04-18 20:20 ` David Brown
2012-04-18 20:39 ` Piergiorgio Sartor
2012-04-19 18:16 ` H. Peter Anvin
2012-04-20 2:27 ` Alex [this message]
2012-04-20 3:00 ` H. Peter Anvin
2012-04-20 3:32 ` Alex
2012-04-20 18:58 ` David Brown
2012-04-20 19:39 ` H. Peter Anvin
2012-04-20 21:04 ` Piergiorgio Sartor
2012-04-20 21:01 ` Piergiorgio Sartor
2012-04-20 21:29 ` Peter Grandi
2012-04-20 22:31 ` Piergiorgio Sartor
2012-04-21 9:51 ` Peter Grandi
2012-04-21 11:18 ` Piergiorgio Sartor
2012-04-22 3:14 ` Alex
2012-04-22 8:57 ` Piergiorgio Sartor
2012-04-20 7:45 ` Stan Hoeppner
2012-04-23 15:26 ` Alex
2012-04-25 1:20 ` Stan Hoeppner
2012-04-25 2:45 ` Alex
2012-04-25 16:59 ` Emmanuel Noobadmin
2012-04-25 19:29 ` David Brown
2012-04-26 2:30 ` Alex
2012-04-27 15:15 ` Emmanuel Noobadmin
2012-05-01 16:38 ` Alex
2012-04-26 4:24 ` Alex
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=CAMqP1GVjqBMTiM9Yb+PxQLULWDnG8x3uvzuLFKya3NXsTPt_hg@mail.gmail.com \
--to=creamyfish@gmail.com \
--cc=hpa@zytor.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).