From: "kedacomkernel" <kedacomkernel@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: question about raid10 near copy info in man mdadm.
Date: Mon, 16 Apr 2012 14:10:28 +0800 [thread overview]
Message-ID: <201204161410242964436@gmail.com> (raw)
In-Reply-To: 201204161346407034012@gmail.com
Why not use md's description instead of mdadm' content?
I think this may be better,especially for people who's native language is not English.
------------------
kedacomkernel
2012-04-16
-------------------------------------------------------------
发件人：NeilBrown
发送日期：2012-04-16 14:01:18
收件人：kedacomkernel
抄送：linux-raid
主题：Re: question about raid10 near copy info in man mdadm.
On Mon, 16 Apr 2012 13:46:46 +0800 "kedacomkernel" <kedacomkernel@gmail.com>
wrote:
> This is the man md about:
> When 'near' replicas are chosen, the multiple copies of a given chunk are laid out consecutively across
> the stripes of the array, so the two copies of a datablock will likely be at the same offset on two
> adjacent devices.
"likely" is different from "certainly". In most cases they are the same
offset. In some cases they are different offsets. I think "likely"
describes that well enough.
>
> I think the word "similar" is the same.
"similar" is not the same as "same", though it is similar .....
"same" means there is no difference.
"similar" means there might be a difference, but it is not a big difference.
Does that clear it up?
NeilBrown
next prev parent reply other threads:[~2012-04-16 6:10 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
2012-04-16 5:46 ` kedacomkernel
2012-04-16 6:01 ` NeilBrown
2012-04-16 6:10 ` kedacomkernel [this message]
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=201204161410242964436@gmail.com \
--to=kedacomkernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.