Package: mdadm
Version: 1.9.0-4sarge1
Severity: Minor
Symptom:
If you are using a redundant RAID level (e.g. 1,5,6) and you have got spare
drives, then mdadm is going to send the "SparesMissing" event at every start
of mdadm.
Problems:
- Package documentation mentions the "SparesMissing" event and mdadm.conf
configuration option "spares=..." only in /usr/shar/doc/mdadm/changelog.gz
with two short unclear sentences.
You have to read the code in order to understand, what this option does and
what the the event means.
Suggested fix:
Add my documentation or write a better one:
-SparesMissing event:
The SparesMissing event will be sent, if
- you have got enough spare drives, but you forgot to specify the
"spares=..." option in your configuration file mdadm.conf
- mdadm --monitor first sees an array and it doesn't have enough spare
devices. I.e you have got a RAID 1/5/6 array up and running, but you
did not specify any spare drives. This means you did not add a so
called
"hot standbye drive". In the case of a drive failure, your array will
be
degraded and cannot be rebuilt automatically.
- spares=... configuration option
This configuration options specifies the number of drives, that are
defined
as spare devices. "mdadm -D /dev/md0" will show these devices as spare
drives
(see below.)
Number Major Minor RaidDevice State
0 33 1 0 active sync /dev/.static/dev/hde1
1 33 65 1 active sync /dev/.static/dev/hdf1
2 34 1 2 active sync /dev/.static/dev/hdg1
3 34 65 3 active sync /dev/.static/dev/hdh1
4 8 2 - spare /dev/.static/dev/sda2
I am using Debian stable GNU/Linux 2.6.17.8
Greetings
Frank
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
