linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: kedacomkernel <kedacomkernel@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: question about raid10 near copy info in man mdadm.
Date: Mon, 16 Apr 2012 15:41:26 +1000	[thread overview]
Message-ID: <20120416154126.2fb059da@notabene.brown> (raw)
In-Reply-To: <201204161328097657740@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Mon, 16 Apr 2012 13:28:14 +0800 "kedacomkernel" <kedacomkernel@gmail.com>
wrote:

> Hi:
> 	I readed the information about raid10 near copy in man mdadm.
> 	It is:
> 	'n' signals 'near' copies.  Multiple copies of one data block are at similar offsets in different
>               devices.
> 	But I think this wrong.
> 	If raid10 had five disks and near copy is equal three.
> 	The layout like:
> 			5 disks
> --------------------
> A1 A1 A1 A2 A2
> A2 A3 A3 A3 A4
> 
> But the copies of datablock A2 are not at similar offset in different device.
> 

They are certainly on different devices so I guess you are questioning the
use of the word "similar".

What do you understand "similar" to mean?

How would you describe offsets which might be the same, or might differ by
one chunk-size?

I'm happy to change the text if it is confusing, but only if the result is
undoubtedly less confusing.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-04-16  5:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  5:28 question about raid10 near copy info in man mdadm kedacomkernel
2012-04-16  5:41 ` NeilBrown [this message]
2012-04-16  5:46   ` kedacomkernel
2012-04-16  6:01     ` NeilBrown
2012-04-16  6:10     ` kedacomkernel
2012-04-16  6:20       ` NeilBrown

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=20120416154126.2fb059da@notabene.brown \
    --to=neilb@suse.de \
    --cc=kedacomkernel@gmail.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).