Activity log for bug #379005

Date Who What changed Old value New value Message
2009-05-21 10:54:17 H.-Dirk Schmitt bug added bug
2009-05-21 10:54:17 H.-Dirk Schmitt attachment added filtered_syslog http://launchpadlibrarian.net/27011161/filtered_syslog
2010-03-29 12:59:18 ceg summary DeviceDisappeared/Wrong-Level monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level
2010-03-29 13:00:57 ceg description Binary package hint: mdadm In the man page it is well documented that monitoring a raid0 device will result in an error message like this: DeviceDisappeared event detected on md device /dev/md3, component device Wrong-Level No email reports are sended, but if you use /sbin/mdadm --follow --scan -1 --syslog your syslog will be flooded (on critical level!) with this irrelevant message. As a workaround I suggest the attached filter example with the command line: /sbin/mdadm --follow --scan -1 --program="filtered_syslog" Binary package hint: mdadm In the man page it is documented that monitoring a raid0 device will result in wrong error message like this: DeviceDisappeared event detected on md device /dev/md3, component device Wrong-Level But they should better be suppressed for raid0. --- No email reports are sended, yet if you use /sbin/mdadm --follow --scan -1 --syslog your syslog will be flooded (on critical level!) with this irrelevant message. As a workaround I suggest the attached filter example with the command line: /sbin/mdadm --follow --scan -1 --program="filtered_syslog"
2010-03-31 10:23:00 ceg summary monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level {upstream} monitoring raid0 floods syslog with DeviceDisappeared/Wrong-Level
2010-03-31 10:57:04 ceg bug task added mdadm