Activity log for bug #497186

Date Who What changed Old value New value Message
2009-12-15 22:11:20 ceg bug added bug
2010-03-07 16:39:13 ceg summary mdadm degrades all arrays (from initramfs) instead of just those required to boot initramfs' mdadm degrades all arrays (not just those required to boot)
2010-03-07 16:51:23 ceg nominated for series Ubuntu Lucid
2010-03-07 16:57:03 ceg description Binary package hint: mdadm The dependencies are not checked, it looks into /proc/mdstat and uses "mdadm --assemble --scan --run". (Additionaly a legacy non-hotplug command.) The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. See https://wiki.ubuntu.com/ReliableRaid Binary package hint: mdadm after a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. The dependencies are not checked and saved to initramfs. Instead the script just looks into /proc/mdstat and uses "mdadm --assemble --scan --run" starting all arrays, if some arrays are incomplete (very likely during initramfs state). (Additionaly a legacy non-hotplug command.) The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. See https://wiki.ubuntu.com/ReliableRaid
2010-03-29 16:36:53 ceg summary initramfs' mdadm degrades all arrays (not just those required to boot) initramfs' init-premount degrades *all* arrays (not just those required to boot)
2010-03-29 16:55:24 ceg description Binary package hint: mdadm after a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. The dependencies are not checked and saved to initramfs. Instead the script just looks into /proc/mdstat and uses "mdadm --assemble --scan --run" starting all arrays, if some arrays are incomplete (very likely during initramfs state). (Additionaly a legacy non-hotplug command.) The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. See https://wiki.ubuntu.com/ReliableRaid After a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. This is not good since non-rootfs arrays are likely to be available only incompletely (due to the early stage during boot) and are getting desynced by this. When creating the initramfs image the mdadm hook should determine the dependencies of the rootfilesystem and save a list of the required md devices in the initramfs. Currently the initramfs boot script just looks for *any* available incomplete array and calls "mdadm --assemble --scan --run", which starts all runnable arrays. -- The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. Bug #491463 upstart init within initramfs
2010-03-29 17:16:30 ceg mdadm (Ubuntu): status New Confirmed
2010-03-30 11:32:59 ceg description After a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. This is not good since non-rootfs arrays are likely to be available only incompletely (due to the early stage during boot) and are getting desynced by this. When creating the initramfs image the mdadm hook should determine the dependencies of the rootfilesystem and save a list of the required md devices in the initramfs. Currently the initramfs boot script just looks for *any* available incomplete array and calls "mdadm --assemble --scan --run", which starts all runnable arrays. -- The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. Bug #491463 upstart init within initramfs After a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. This is not good since non-rootfs arrays are likely to be available only incompletely (due to the early stage during boot) and are getting desynced by this. When creating the initramfs image the mdadm hook should determine the dependencies of the rootfilesystem and save a list of the required md devices in the initramfs. See: How would you decide what device is needed? at https://wiki.ubuntu.com/ReliableRaid Currently the initramfs boot script just looks for *any* available incomplete array and calls "mdadm --assemble --scan --run", which will start *all* runnable arrays. --- comment #2 contains a workaround for the proper command to run single arrays degraded.