That change could more be a source of what you describe.
It contains a huge set of backports in regard to ignore "local non-mpath
devices"
* Cherry-picked patches to ignore local non-mpath devices
- 0001-multipath-add-checker_timeout-default-config-option.patch
- 0002-Make-params-variable-local.patch
- 0003-libmultipath-Fix-possible-string-overflow.patch
- 0004-Update-hwtable-factorization.patch
- 0005-Fixup-strip-trailing-whitespaces-for-getuid-return-v.patch
- 0006-Remove-sysfs_attr-cache.patch
- 0007-Move-setup_thread_attr-to-uevent.c.patch
- 0008-Use-lists-for-uevent-processing.patch
- 0009-Start-uevent-service-handler-from-main-thread.patch
- 0010-libmultipath-rework-sysfs-handling.patch
- 0011-Rework-sysfs-device-handling-in-multipathd.patch
- 0012-Only-check-offline-status-for-SCSI-devices.patch
- 0013-Check-for-offline-path-in-get_prio.patch
- 0014-libmultipath-Remove-duplicate-calls-to-path_offline.patch
- 0015-Update-dev_loss_tmo-for-no_path_retry.patch
- 0016-Reload-map-for-device-read-only-setting-changes.patch
- 0017-multipath-get-right-sysfs-value-for-checker_timeout.patch
- 0018-multipath-handle-offlined-paths.patch
- 0019-multipath-fix-scsi-timeout-code.patch
- 0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch
- 0021-multipath-cleanup-dev_loss_tmo-issues.patch
- 0022-Fix-for-setting-0-to-fast_io_fail.patch
- 0023-Fix-fast_io_fail-capping.patch
- 0024-multipath-enable-getting-uevents-through-libudev.patch
- 0025-Use-devpath-as-argument-for-sysfs-functions.patch
- 0026-multipathd-remove-references-to-sysfs_device.patch
- 0027-multipathd-use-struct-path-as-argument-for-event-pro.patch
- 0028-Add-global-udev-reference-pointer-to-config.patch
- 0029-Use-udev-enumeration-during-discovery.patch
- 0030-use-struct-udev_device-during-discovery.patch
- 0031-More-debugging-output-when-synchronizing-path-states.patch
- 0032-Use-struct-udev_device-instead-of-sysdev.patch
- 0033-discovery-Fixup-cciss-discovery.patch
- 0035-Use-udev-devices-during-discovery.patch
- 0036-Remove-all-references-to-hand-craftes-sysfs-code.patch
- 0037-multipath-libudev-cleanup-and-bugfixes.patch
- 0038-multipath-check-if-a-device-belongs-to-multipath.patch
- 0039-multipath-and-wwids_file-multipath.conf-option.patch
- 0040-multipath-Check-blacklists-as-soon-as-possible.patch
- 0041-add-wwids-file-cleanup-options.patch
- 0042-add-find_multipaths-option.patch
Your devices are reported as:
mpath2 (36742b0f0000075500000000000002de4) dm-2 NFINIDAT,InfiniBox
size=954M features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=-1 status=active
`- 2:0:0:3 sdd 8:48 active undef running
Maybe there is a false positive in those fixes.
To continue on this we need very exact description on your device type,
storage backend, and anything else that defines your disk setup in
HW&SW.
Then depending on availability of such devices or at least a similar
setup a reproduction can be tried - if not possible one might suggest
different things to be tested on your end, but that is way slower and
more error prone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629644
Title:
Trusty: failure to detect device with 0.4.9-3ubuntu7.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1629644/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
