[Bug 1432062] Re: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers

Launchpad Bug Tracker 1432062 at bugs.launchpad.net
Mon Feb 15 23:15:28 UTC 2016


This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu7.9

---------------
multipath-tools (0.4.9-3ubuntu7.9) trusty; urgency=medium

  * debian/patches/kpartx-support-device-names-with-spaces.patch: fix loopback
    files unmapping. (LP: #1543430)

multipath-tools (0.4.9-3ubuntu7.8) trusty; urgency=medium

  * debian/patches/kpartx-support-device-names-with-spaces.patch: deal with
    spaces in device names in kpartx too (LP: #1432062)
  * debian/initramfs/local-premount: wait for udev to settle before mounting
    so the by-uuid/ symlinks have a chance to be updated by udev rules.
    (LP: #1503286)
  * Allow device detection all through the initramfs: run multipathd instead
    of only scanning once for devices, so those that come up slower can still
    be used as a root device (LP: #1526984):
    - debian/patches/0050-readonly-bindings_prefix.patch,
      debian/patches/0051-readonly-bindings_multipath.patch,
      debian/patches/0052-readonly-bindings_multipathd.patch,
      debian/patches/0053-readonly-bindings_multipathd_prod.patch: support -B
      to allow multipathd to handle cases where the bindings file is read-only.
    - debian/initramfs/hooks: install multipathd and required directories.
    - debian/initramfs/local-premount: also reload all maps to make sure
      they're ready before we mount.
    - debian/initramfs/local-top: run multipathd rather than a one-off call to
      multipath so that new paths can be correctly added as detected while
      we're still in the initramfs.
    - debian/initramfs/local-bottom: remember to stop multipathd.
    - debian/initramfs/local-bottom, debian/rules: install local-bottom for
      initramfs.
  * debian/patches/lp1496210_add_IBM_XIV_defaults.patch: add support (default
    config values) for the IBM 2810XIV storage system. (LP: #1496210)
  * debian/patches/0054-kpartx-update-option.patch: run kpartx -u rather than
    kpartx -a, so as to remove old partition entries if the partition table
    has changed. (LP: #1473903)
  * debian/patches/multipath_enable_sync_support_1b8082c8.patch,
    debian/patches/kpartx_rely_on_udev_dev_creation_9a632fff.patch: synchronize
    udev, device-mapper and multipath, and let udev deal with creating device
    nodes and symlinks. (LP: #1486370)
  * debian/initramfs/local-top: drop scsi_wait_scan stanza, that module is no
    longer available. (LP: #1538775)

 -- Mathieu Trudel-Lapierre <mathieu-tl at ubuntu.com>  Tue, 09 Feb 2016
16:03:10 -0500

** Changed in: multipath-tools (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

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

Title:
  multipath-tools-boot: support booting without user_friendly_names on
  devices with spaces in identifiers

Status in multipath-tools package in Ubuntu:
  Fix Released
Status in multipath-tools source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed.
  If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support.
  Those rules don't handle disk devices w/ spaces on their names/uuids/models very well..

  That's because of udev's SYMLINK command using spaces to separate
  multiple links, and the kernel sysfs/dm informing \x20 instead, which
  is not correctly interpreted by some commands, resulting in file not
  found errors, for example.

  Thus, the system fails to boot.

  [Test case]
  Requires installing on a system where there are spaces in the name of the device make/model data; for instance, on POWER8 with IPR disks, or with QEMU.
  1) Install system with multipath support ('disk-detect/multipath/enable=true').
  2) Boot the system.
  3) Edit /etc/multipath.conf, remove "user_friendly_names yes" ; replace with "user_friendly_names no", or remove /etc/multipath.conf.
  4) Update the initramfs: sudo update-initramfs -u
  5) Reboot.

  [Regression potential]
  Minimal. Systems with names in the disk make/model data would not boot without user_friendly_names enabled. This patch will allow multipath-tools to correctly handle these devices in the case where friendly names are not enabled by using the devices major/minor numbers rather that its path.

  ----

  There's no problem, however, if user_friendly_names is enabled in
  multipath.conf (which is enabled in the default multipath.conf from
  the installer, if it has multipath enabled).

  Notice it's an acceptable case to install w/out multipath support, and
  enable it later for booting.

  Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example:
  - IBM IPR  ( IBM     IPR-0   5DB6F40000000080 )
  - IBM VDASD ( AIX     VDASD           00c96f0700004c000000014bb8e713f0.14 )
  - QEMU HARDDISK ( QEMU QEMU HARDDISK <serial> )

  So, please, is it possible to ship the default multipath.conf (e.g.,
  from installer) w/ multipath-tools-boot?

  For users not to their systems failing to boot after installing
  multipath-tools-boot manually, after a non-multipath install.

  Related bugs:
   * bug 1371634: block devices appear twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+subscriptions



More information about the foundations-bugs mailing list