Document SparesMissing and DeviceDisappeared/WrongLevel

Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>

2 files changed, 23 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index c78a97e..12e94ef 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,6 +2,7 @@ Changes Prior to 1.12.0 release
     -   Don't use 'lstat' to check for blockdevices, use stat.
     -   Get size calculation right when in Create when BLKGESIZE64 not available
     -   Document --size=max option for --grow
+    -   Document SparesMissing event and DeviceDisappeared/WrongLevel
 	
 Changes Prior to 1.11.0 release
     -   Fix embarassing bug which causes --add to always fail.
diff --git a/mdadm.8 b/mdadm.8
index 1a34690..bbe50b2 100644
--- a/mdadm.8
+++ b/mdadm.8
@@ -1009,6 +1009,16 @@ The different events are:
 An md array which previously was configured appears to no longer be
 configured.
 
+If
+.I mdadm
+was told to monitor an array which is RAID0 or Linear, then it will
+report
+.B DeviceDisappeared
+with the extra information
+.BR Wrong-Level .
+This is because RAID0 and Linear do not support the device-failed,
+hot-spare and resync operations which are monitored.
+
 .TP
 .B RebuildStarted
 An md array started reconstruction.
@@ -1061,6 +1071,18 @@ A spare drive has been moved from one array in a
 to another to allow a failed drive to be replaced.
 
 .TP
+.B SparesMissing
+If
+.I mdadm
+has been told, via the config file, that an array should have a certain
+number of spare devices, and
+.I mdadm
+detects that it has fewer that this number when it first sees the
+array, it will report a
+.B SparesMissing
+message.
+
+.TP
 .B TestMessage
 An array was found at startup, and the
 .B --test