Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: NeilBrown <neilb@suse.com>,
	Wol's lists <antlists@youngman.org.uk>,
	mdraid <linux-raid@vger.kernel.org>
Subject: Re: RFC - de-clustered raid 60 or 61 algorithm
Date: Thu, 8 Feb 2018 07:56:10 -0500	[thread overview]
Message-ID: <e7c2c26c-c59b-ebab-423d-683a05ddfd8c@turmel.org> (raw)
In-Reply-To: <876078maui.fsf@notabene.neil.brown.name>

On 02/07/2018 10:14 PM, NeilBrown wrote:
> On Thu, Feb 08 2018, Wol's lists wrote:

>> I've been playing with a mirror setup, and if we have two mirrors, we 
>> can rebuild any failed disk by coping from two other drives. I think 
>> also (I haven't looked at it) that you could do a fast rebuild without 
>> impacting other users of the system too much provided you don't swamp 
>> i/o bandwidth, as half of the requests for data on the three drives 
>> being used for rebuilding could actually be satisfied from other drives.
> 
> I think that ends up being much the same result as a current raid10
> where the number of copies doesn't divide the number of devices.
> Reconstruction reads come from 2 different devices, and half the reads
> that would go to them now go elsewhere.

This begs the question:

Why not just use the raid10,near striping algorithm?  Say one wants
raid6 n=6 inside raid60 n=25.  Use the raid10,near6 n=25 striping
algorithm, but within each near6 inner stripe place data and P and Q
using the existing raid6 rotation.

What is the more complex placement algorithm providing?

Phil

  reply	other threads:[~2018-02-08 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08  0:46 RFC - de-clustered raid 60 or 61 algorithm Wol's lists
2018-02-08  3:14 ` NeilBrown
2018-02-08 12:56   ` Phil Turmel [this message]
2018-02-08 23:10     ` Wol's lists
2018-02-09 23:12   ` Wol's lists
2018-02-10  3:02   ` John Stoffel

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=e7c2c26c-c59b-ebab-423d-683a05ddfd8c@turmel.org \
    --to=philip@turmel.org \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    /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