tags 559390 moreinfo thanks also sprach Ross Boylan <r...@biostat.ucsf.edu> [2009.12.05.0926 +1300]: > The original primary issue, the lack of information in the log > that the array is degraded, probably only warrants minor severity, > given that there is an email report.
The mdadm monitor does log to syslog: Jan 26 23:51:02 mdadm-lab mdadm[1432]: Fail event detected on md device /dev/md1, component device /dev/vde This is because /etc/default/mdadm defines DAEMON_OPTIONS="--syslog" so see mdadm(8) for the rest. checkarray is not responsible for reporting problems. If you think this should be handled differently, please report a separate issue. > The second issue, the lack of auto-reconstruction of the degraded > array, might warranty higher severity. I need more information. What exactly do you want? If /dev/md0 is made up of /dev/sd[ab]1 and /dev/sdb1 is faulty and removed from the array, do you want mdadm to automatically re-add /dev/sdb1 upon the next reboot?? What if /dev/sdb1 is still the faulty drive? -- .''`. martin f. krafft <madd...@d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
