mdadm (2.4.1-6ubuntu5) edgy; urgency=low
  
  * Modify initrafms scripts to wait for devices to appear if they are not there
    yet when the script is executed on boot:
    - copy generated mdadm.conf in the initramfs (we need the UUIDs)
    - modify local-top script to wait for all UUIDs to appear before executing
      mdrun or wait a max of 3 minutes before giving up.
  (Closes Ubuntu: #52740)
  As a side effects of the above fix:
  
  * Avoid FileSystem corruption if root is on lvm on raid and raid is not
    started. LVM will find the devices that are part of the raid and use them
    bringing the data off-sync.

  Limitations:

  * It might require initramfs updates if raid UUIDs are changed. This is
    a rare corner case of relocating raids and usually who does that knows
    what he is doing.

  * We do not check if all devices for a certain raids are available but
    the machine might be booting in degraded mode for recovery and we
    shouldn't be blocking on that. Given that there is no way to know that
    this check will not be performed.

 -- Fabio M. Di Nitto <[EMAIL PROTECTED]>  Tue, 26 Sep 2006 09:56:01
+0200


** Changed in: mdadm (Ubuntu)
       Status: Confirmed => Fix Released

-- 
[EDGY] Regression: can't boot from lvm root on raid anymore
https://launchpad.net/bugs/52740

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to