linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: Mark Knecht <markkecht@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH mdadm 1/1] Clarify scope of Rebuild events in mdadm manpage
Date: Thu, 12 Dec 2013 13:26:53 +1100	[thread overview]
Message-ID: <20131212132653.28f56053@notabene.brown> (raw)
In-Reply-To: <1386747955-7238-1-git-send-email-jan.ceuleers@computer.org>

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

On Wed, 11 Dec 2013 08:45:55 +0100 Jan Ceuleers <jan.ceuleers@computer.org>
wrote:

> To date, the manpage did not make it clear under which circumstances
> Rebuild events are generated, leading to a question on the mailing
> list as to whether it is normal for these events to be generated
> while checking an array.
> So clarify that all operations that act on the entire array are in
> scope. The list is given as "e.g.", because it might grow in the
> future as other full-array operations are added.
> 
> Reported-by: Mark Knecht <markknecht@gmail.com>
> Signed-off-by: Jan Ceuleers <jan.ceuleers@computer.org>
> ---
>  mdadm.8.in |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mdadm.8.in b/mdadm.8.in
> index edbedc4..ced1b50 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -2363,7 +2363,8 @@ hot-spare and resync operations which are monitored.
>  
>  .TP
>  .B RebuildStarted
> -An md array started reconstruction. (syslog priority: Warning)
> +An md array started reconstruction (e.g. recovery, resync, reshape,
> +check, repair). (syslog priority: Warning)
>  
>  .TP
>  .BI Rebuild NN

Applied, thanks.

NeilBrown

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

           reply	other threads:[~2013-12-12  2:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1386747955-7238-1-git-send-email-jan.ceuleers@computer.org>]

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=20131212132653.28f56053@notabene.brown \
    --to=neilb@suse.de \
    --cc=jan.ceuleers@computer.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=markkecht@gmail.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;
as well as URLs for NNTP newsgroup(s).