Bug#376009: mdadm: AUTOSTART should control the stopping of arrays as well and default to off

[martin f krafft]

also sprach Christian Pernegger <pernegger at gmail.com> [2006.06.29.1820 +0200]:
> - the shipping configuration of mdadm tries to start all md arrays in
> the machine at startup and postinst, which includes arrays the user
> did not want started for any reason. This is especially bad if disks
> with (obsolete) RAID superblocks have just been added to the machine.
> This behaviour can be changed via debconf variable, however the
> questions are not shown at the default debconf priority, and after the
> install it is too late.

Would it help if I asked the question at higher priority?

Also, I am not sure about setting the default to off as it may leave
users with unusable systems. But then, I am ambivalent about it,
really.

> - regardless of the AUTOSTART setting the init script tries to
> shutdown all arrays on "stop". IMO, if the script is told not to start
> arrays it shouldn't stop any, either.

This is true.

> - (some of the other bug reports suggest initrd integration,
> though I couldn't find any in the package's files. I just hope
> this doesn't interfere with EVMS's initrd integration ... )

initrd integration has been there for years. I am working on
initramfs.

If you'd help me out we can make sure that there's not inteference.

-- 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
remember, half the people you know are below average.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20060629/4a49b1a6/attachment.pgp