[Bug 968074] Re: Partitionable raid ignored by 65-mdadm-blkid.rules

[Dmitrijs Ledkovs]

Everything below was done on precise:

I do agree that the standard partitionable mdadm raid devices
(/dev/md_dNNpXX) were not supported in precise, but now are supported
with the version from -proposed.

But please note that even though I created /dev/md_d1, /dev/md_d1p1 and
/dev/md_d1p2 the device names have changed after the reboot to
/dev/md127, /dev/md127p1, /dev/md127p2 which is interesting. As long as
you use UUID to mount filesystems everything should be fine, or create
the md device with stable names e.g. /dev/md/myraid with partitions
/dev/mdmyraid1 /dev/mdmyraid2, as those names will stay stable.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/968074

Title:
  Partitionable raid ignored by 65-mdadm-blkid.rules

Status in “mdadm” package in Ubuntu:
  Fix Released
Status in “mdadm” source package in Precise:
  Fix Committed
Status in “mdadm” source package in Quantal:
  Fix Released

Bug description:
  [IMPACT]

   * Partitionable raid1 arrays following the /dev/md_d[0-9]* naming
  convention were ignored by the default udev settings.

   * Thus it prevents booting, if rootfs is on the partitioned RAID
  array, since that would never be assembled by udev rules

   * This is fixed by switching from dated Ubuntu udev rules, to the now
  shipped in the upstream udev rules

  [TESTCASE]

   * Add partitioned RAID1 to the system
   * Notice that it doesn't get assembled
   * Upgrade the package
   * Re-add partitioned RAID1 to the system
   * Notice that it does get assembled

  [Regression Potential]

   * The default udev rule has changed. Users who relied on the
  previous, incomplete/broken, behaviour may be pleasantly surprised or
  annoyed that  by-hand assembly of partitioned RAID arrays is not
  longer required.

   * System administrators need to check their /etc/udev/rules.d/ to
  make sure that (a) they do not override mdadm rules (b) if they do,
  check that those overrides are still needed (c) that the override is
  named to match the new udev rule name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/968074/+subscriptions