* Re: [PATCH mdadm 1/1] Clarify scope of Rebuild events in mdadm manpage
[not found] <1386747955-7238-1-git-send-email-jan.ceuleers@computer.org>
@ 2013-12-12 2:26 ` NeilBrown
0 siblings, 0 replies; only message in thread
From: NeilBrown @ 2013-12-12 2:26 UTC (permalink / raw)
To: Jan Ceuleers; +Cc: Mark Knecht, linux-raid
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread