also sprach Michael Evans <mjevans1983@gmail.com> [2010.02.22.0837 +0100]: > I don't know how whatever was mentioned previously would work for > that, but I do have a solution. […] > Incremental assembly, or examine with all block devices to > generate a new mdadm.conf file. Please see the thread for reasons why incremental assembly works only with an mdadm.conf file, or if you can uniquely identify the system before the root filesystem is mounted. Please see the thread for reasons why unconditional auto-assembly of all available arrays may not be desirable. > Presuming you have a consistently labeled rootfs in your > deployment (say mandating that the / filesystem be labeled 'root' > or some other value and that no other FS may share that same > label) then it should work out just fine. I fundamentally agree. However, driving this change from mdadm will be impossible. If that is the way to go, then we must first ensure that device names become deprecated, and that everyone uses /dev/disk/by-uuid/*. Only then can we start relying on it. -- .''`. martin f. krafft <madduck@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
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)