Bug#552130: A *boot* order problem...

[Bjørn Mork]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: y
Type: text/x-diff
Size: 384 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20100117/1b5af1fc/attachment.diff>