Comment 2 for bug 681391

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dmraid - 1.0.0.rc16-4ubuntu1

---------------
dmraid (1.0.0.rc16-4ubuntu1) natty; urgency=low

  * Merge from debian unstable (LP: #681391), remaining changes:
    - debian/dmraid-activate: Remove the special-casing of the root
      device which breaks in many situations and leaves the raw devices
      exposed. This was introduced in Debian to accommodate some broken
      configurations which wanted to access "partitions" on the raid
      raw devices. In Ubuntu, broken configurations has not been supported.
    - debian/dmraid.postinst: Comment out "udevadm trigger" call in postinst
      for now as it has severeconsequences when mountall is installed
      (clears /tmp). If dmraid is installed, then presumably the important
      system devices are up and one can be bothered with a reboot to take
      the change into account. Let update-initramfs flag the system
      as needing a reboot.
    - Removed |change udev rule for dmraid-activate to prevent infinite udev
      event loop (LP: #534743).

dmraid (1.0.0.rc16-4) unstable; urgency=low

  [ Modestas Vainius ]
  * [7b2bf79] Make dmraid-activate work with DDF1 arrays by special-
    casing their handling. Similar to ISW case, there do not seem to be
    a way for getting raid subsets for the physical drive except parsing
    native log. (Closes: #603319)
 -- Lorenzo De Liso <email address hidden> Thu, 25 Nov 2010 14:43:17 +0100