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

[martin f krafft]

also sprach Bjørn Mork <bjorn at mork.no> [2010.01.18.0947 +1300]:
> 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".

Where is the write-intent bitmap stored? /lib/init/rw is available
r/w even before checkroot. I'd rather not move mdadm-raid around
because it took months to settle on the current position. So
instead, we should make sure that mdadm knows where to try to drop
its files.

-- 
 .''`.   martin f. krafft <madduck at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20100119/8676937b/attachment.pgp>