linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Martin <oliver@volatilevoid.net>
To: Dan Williams <dan.j.williams@intel.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Creating a 3-disk RAID6 array
Date: Fri, 18 May 2012 01:27:02 +0200	[thread overview]
Message-ID: <4FB58946.2050508@volatilevoid.net> (raw)
In-Reply-To: <CAA9_cmd=tXvfWkgm1efsZmaWMgXQeuOdX0pAHrLC_-KejyseKw@mail.gmail.com>

Am 17.05.2012 23:02, schrieb Dan Williams:
>> I'll have to leave for for hpa to answer.  I've occasionally thought that
>> maybe it should be fixed, but it never seemed worth the effort.
>
> The math assumes 2 data disks.

Aside from a BUG_ON in async_raid6_datap_recov, it seems like it should 
work based on a cursory glance. Especially the various gen_syndrome 
implementations and raid6_datap_recov look like they should produce the 
correct result.

>> Yes, not possible at present.
>> It might be as simple and finding the places that impose the limit and delete
>> them...
>
> You'd certainly need to route around the acceleration code, because
> that increased the dependency on the assumption that there is always
> two data disk slots.

This, however, makes it seem like lots of hassle for very little gain, 
given that the same on-disk data can much more cheaply be produced by 
using a RAID1. I think the more sensible thing to do is to add support 
for reshaping a RAID1 into a 4-disk RAID6. This should hopefully not be 
too different from the existing RAID5-RAID6 reshape, and is probably 
what I'll (at least try to) implement when the time comes to expand my 
array.

Oliver

  reply	other threads:[~2012-05-17 23:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  1:24 Creating a 3-disk RAID6 array Oliver Martin
2012-05-17  1:38 ` NeilBrown
2012-05-17 13:18   ` David Brown
2012-05-17 14:04     ` John Robinson
2012-05-18  7:24       ` David Brown
2012-05-18  7:30       ` H. Peter Anvin
2012-05-18  7:57         ` NeilBrown
2012-05-19  0:04           ` H. Peter Anvin
2012-05-17 21:02   ` Dan Williams
2012-05-17 23:27     ` Oliver Martin [this message]
2012-05-17  4:22 ` Bill Davidsen
2012-05-18  2:36 ` Stan Hoeppner

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=4FB58946.2050508@volatilevoid.net \
    --to=oliver@volatilevoid.net \
    --cc=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).