tags 552130 +patch thanks This turns out to be a mere boot order problem. At the time /etc/init.d/mdadm-raid is run, no file system is writeable yet and using a write intent bitmap is therefore impossible. This should either be documented or fixed.
I suggest the attached patch, supporting a write intent bitmap on the root filesystem. This should be safe(?) as the root file system must have been started in the initramfs anyway even if it is on a md device. The patch seems to solve my problem, after running "insserv -d". Bjørn
--- /etc/init.d/mdadm-raid.orig 2009-11-06 10:10:30.000000000 +0100 +++ /etc/init.d/mdadm-raid 2010-01-17 21:34:36.000000000 +0100 @@ -8,7 +8,7 @@ # ### BEGIN INIT INFO # Provides: mdadm-raid -# Required-Start: mountkernfs +# Required-Start: mountkernfs checkroot # Should-Start: udev devfsd # Required-Stop: mountkernfs # Should-Stop: udev devfsd
