From: CoolCold <coolthecold@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] Update documentation for sync_min and sync_max entries
Date: Wed, 11 May 2011 21:11:39 +0400 [thread overview]
Message-ID: <BANLkTi=qU-7UX6SGrfLX3wNRUPOKzDSwgg@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinEzjxW6ZFkBWYc6UY6Pus1NoY_O+bKyCoDgC6w@mail.gmail.com>
There is orthographical mistake in patch, in word "withing", should be
"within". I guess this is too little for one more emailed patch, so
just notifying & marking line.
On Tue, Mar 15, 2011 at 3:30 PM, CoolCold <coolthecold@gmail.com> wrote:
> This patch is against 2.6.37 (
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.37.y.git
> , commit id 97b197f07d15dbcd53328e75754e2f947814c733 ) but I didn't
> notice any changes in 2.6.38 though.
>
> linux/Documentation/md.txt is missing description for sync_min and
> sync_max entries.
> This patch adds description for sync_min and sync_max entries.
>
> Signed-off-by: Roman Ovchinnikov <coolthecold@gmail.com>
> ---
> Documentation/md.txt | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/md.txt b/Documentation/md.txt
> index a81c7b4..8f8cb4f 100644
> --- a/Documentation/md.txt
> +++ b/Documentation/md.txt
> @@ -552,6 +552,16 @@ also have
> within the array where IO will be blocked. This is currently
> only supported for raid4/5/6.
>
> + sync_min
> + sync_max
> + The two values, given as numbers of sectors, indicate a range
-+ withing the array where 'check'/'repair' will operate. Must be
++ within the array where 'check'/'repair' will operate. Must be
> + a multiple of chunk_size. When it reaches "sync_max" it will
> + pause, rather than complete.
> + You can use 'select' or 'poll' on "sync_completed" to wait for
> + that number to reach sync_max. Then you can either increase
> + "sync_max", or can write 'idle' to "sync_action".
> +
>
> Each active md device may also have attributes specific to the
> personality module that manages it.
>
--
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-11 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 12:30 [PATCH] Update documentation for sync_min and sync_max entries CoolCold
2011-03-18 2:34 ` NeilBrown
2011-05-11 17:11 ` CoolCold [this message]
2011-05-11 23:11 ` 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='BANLkTi=qU-7UX6SGrfLX3wNRUPOKzDSwgg@mail.gmail.com' \
--to=coolthecold@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 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).