From: NeilBrown <neilb@suse.de>
To: keld@keldix.com
Cc: Brassow Jonathan <jbrassow@redhat.com>,
dm-devel@redhat.com, linux-raid@vger.kernel.org, agk@redhat.com
Subject: Re: [PATCH v2] DM RAID: Add support for MD RAID10
Date: Fri, 13 Jul 2012 11:27:17 +1000 [thread overview]
Message-ID: <20120713112717.3b15647c@notabene.brown> (raw)
In-Reply-To: <20120713011505.GA3099@www5.open-std.org>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Fri, 13 Jul 2012 03:15:05 +0200 keld@keldix.com wrote:
> I think the layout you described should not be promoted at all,
> and only kept for backward compatibility. As there is no backward
> compatibility in your case I think it is an error to implement it.
> I understand that you do not reuse any of the MD code here?
Not correct. The whole point of this exercise is to reuse md code.
> The flaw is worse than Neil described, as far as I understand.
> With n=2 you can in the current implementation only have 1 disk failing,
> for any numbers of drives in the array. With the suggested layout
> then for 4 drives you have the probability of surviving 66 %
> of 2 drives failing. This get even better for 6, 8 .. disks in the array.
> And you may even survive 3 or more disk failures, dependent on the number
> of drives employed. The probability is the same as for raid-1+0
Also not correct. You can certainly have more than one failed device
providing you don't have 'n' adjacent devices all failed.
So e.g. if you have 2 drives in a far-2 layout then you can survive the
failure of three devices if they are 0,2,4 or 1,3,5.
>
> > When it is available to MD, I'll make it available to dm-raid also.
>
> Please dont implement it in the flawed way. It will just create a number of problems
> for when to switch over and convert between the two formats, and then which should
> be the default (I fear some would say the old flawed should be the default), and we need
> to explain the two formats and implement two sets of repairs and so on.
This "flawed" arrangement is the only one that makes sense for an odd number
of devices (assuming 2 copies).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-13 1:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 1:36 [PATCH v2] DM RAID: Add support for MD RAID10 Jonathan Brassow
2012-07-12 6:32 ` NeilBrown
2012-07-12 9:56 ` Alasdair G Kergon
2012-07-12 11:43 ` NeilBrown
2012-07-16 22:06 ` Brassow Jonathan
2012-07-17 2:34 ` NeilBrown
2012-07-17 16:15 ` Brassow Jonathan
2012-07-18 1:11 ` NeilBrown
2012-07-18 14:45 ` Brassow Jonathan
2012-07-12 16:22 ` keld
2012-07-12 19:00 ` Brassow Jonathan
2012-07-13 1:15 ` keld
2012-07-13 1:27 ` NeilBrown [this message]
2012-07-13 8:29 ` keld
2012-07-16 6:14 ` NeilBrown
2012-07-16 8:28 ` keld
2012-07-16 22:53 ` Brassow Jonathan
2012-07-17 2:29 ` NeilBrown
2012-07-17 20:30 ` Brassow Jonathan
2012-07-17 2:40 ` NeilBrown
2012-07-18 7:20 ` keld
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=20120713112717.3b15647c@notabene.brown \
--to=neilb@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jbrassow@redhat.com \
--cc=keld@keldix.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).