** Description changed: Binary package hint: debian-installer On systems that are set up statically mdadm.conf is often used to list the md devices that should be set up and the startup script just calls mdadm --assemble --scan. But on systems oriented towards hotplug ability this prevents arrays from being assembled by the hotplug system. Ubuntu has switched to set up complete (non-degraded) arrays automatically with udev rules. But any ARRAY line in mdadm.conf created during (package) installation prevents the hotplugging to work with other arrays. - As only complete (non-degraded) arrays are run automatically the - automatic assembly will leave partial arrays that may be plugged in - untouched, thus the system shoud be save even without the ARRAY - restriction. + As in general only complete (non-degraded) arrays should be run + automatically, the automatic assembly will leave partial arrays that may + be plugged in untouched, thus the system shoud be save even without the + ARRAY restriction. (The --no-degraded and --increamental options have been implemented with this hotplugging in mind.) - The ARRAY lines should not be created on udev+mdadm systems. + The installer should not create the ARRAY lines on udev+mdadm systems + because this breaks further raid setups.
** Summary changed: - raid setup fails due to mdadm.conf with explicit ARRAY statements and HOMEHOST !=any + raid setups fail due to mdadm.conf with explicit ARRAY statements and HOMEHOST !=any -- raid setups fail due to mdadm.conf with explicit ARRAY statements and HOMEHOST !=any https://bugs.launchpad.net/bugs/252345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
