Bug#398310: Re: Bug#398310: don't assemble all arrays on install

[martin f krafft]

also sprach dean gaudet <dean at arctic.org> [2006.11.13.1116 +0100]:
> right, now i know that i should create an /etc/default/mdadm
> *before* i install mdadm... because unlike other packages, mdadm
> does potentially dangerous things just by installing it.  i'll
> keep that in mind :)

You could also just reconfigure your debconf to show questions of
low priority; since you're juggling disks, it seems like that's the
more appropriate level.

I have raised the question for INITRDSTART to high priority.

> i think the only solution is to go entirely event based... start
> meshing into udev or something.  you'd have to be able to express
> the dependencies of a device/filesystem somehow though.  ugh.

we have plans into this direction.

> actually, after playing with the disks with md, and then moving
> them into 3ware hardware raid, i did zero the disks... through the
> 3ware hw raid.  the problem is that the 3ware hw raid superblock
> is even larger than the md raid superblock (100MB vs. a few MB in
> my limited experiments)... so even though i zeroed the hw raid
> device it went nowhere near the stale md superblock (even the
> 3ware hw raid superblock never touched it).

they are likely at opposite ends of the disk.

-- 
 .''`.   martin f. krafft <madduck at debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  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: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20061113/c1b24d2f/attachment.pgp