I am also affected by this bug, and it also seems like whatever *is* starting mdadm is not setting the pidfile options correctly, so that the file /run/mdadm/monitor.pid does not contain the correct pid of the running process.

--
Stephen Paul Weber, @singpolyma
See <http://singpolyma.net> for how I prefer to be contacted
edition right joseph

Reply via email to