From 2ca20929fa2471bf485218ed37a01ab36d160f17 Mon Sep 17 00:00:00 2001 From: Jan Ceuleers Date: Wed, 11 Dec 2013 08:45:55 +0100 Subject: [PATCH] Clarify scope of Rebuild events in mdadm manpage 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 Signed-off-by: Jan Ceuleers Signed-off-by: NeilBrown --- mdadm.8.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mdadm.8.in b/mdadm.8.in index edbedc40..ced1b509 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 -- 2.47.2