| 2008-07-27 14:57:42 |
ceg |
bug |
|
|
added bug |
| 2009-01-31 13:46:31 |
Martin Mai |
debian-installer: status |
New |
Incomplete |
|
| 2009-01-31 13:46:31 |
Martin Mai |
debian-installer: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. |
|
| 2009-11-25 20:03:02 |
ceg |
summary |
mdadm.conf is crated with explicit ARRAY statements prevents hotplug autodetection |
mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection |
|
| 2009-11-25 20:07:43 |
ceg |
debian-installer (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2010-03-07 17:01:32 |
ceg |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-03-07 17:03:28 |
ceg |
summary |
mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection |
mdadm.conf created with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection |
|
| 2010-03-07 17:57:19 |
ceg |
summary |
mdadm.conf created with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug autodetection |
mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug setup |
|
| 2010-03-07 18:03:41 |
ceg |
summary |
mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug setup |
raid setup fails due to mdadm.conf with explicit ARRAY statements and HOMEHOST !=any |
|
| 2010-03-07 18:10:28 |
ceg |
description |
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.
(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. |
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 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 installer should not create the ARRAY lines on udev+mdadm systems because this breaks further raid setups.
|
|
| 2010-03-07 18:11:12 |
ceg |
summary |
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 |
|
| 2011-05-01 08:34:21 |
Till Ulen |
removed subscriber Alexander Konovalenko |
|
|
|
| 2012-03-03 08:28:40 |
Stefan Eggers |
bug |
|
|
added subscriber Stefan Eggers |
| 2012-12-17 17:45:46 |
Grant Slater |
bug |
|
|
added subscriber Grant Slater |
| 2013-05-06 07:11:07 |
Stefan Eggers |
removed subscriber Stefan Eggers |
|
|
|
