** Changed in: multipath-tools (Ubuntu Trusty)
Milestone: None => trusty-updates
** Changed in: multipath-tools (Ubuntu Vivid)
Milestone: None => vivid-updates
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
** Also affects: multipath-tools (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu Trusty)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-t
This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu2
---
multipath-tools (0.5.0-7ubuntu2) wily; urgency=medium
* debian/patches/add_find-multipaths.patch: properly handle local non-mpath
devices. (LP: #1463046)
* debian/patches/ignore_devices_nodename_fail.patch:
** Branch linked: lp:~mathieu-tl/ubuntu/vivid/multipath-tools/SRUs-
fastio-usb-findmpath
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1463046
Title:
installation of multip
Could you please run 'udevadm info --query=all --name=/dev/sda' so we
know whether there are attributes we can use to differentiate these
drives?
** Changed in: multipath-tools (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
In light of this, I'm guessing we'll need to special-case these devices
to use page 0x80 to decide whether to consider them as multipath
devices, at least on 14.04.
For 15.10; I'd like to run a bit more testing, I believe multipath-tools
0.5.0 / sg3-utils will make changes unnecessary and properly
% for p in 0x80 0x83 pre-spc3-83; do
for d in /dev/sd?; do [ -b "$d" ] || continue;
printf "page %-12s: %s: '%s'\n" "$p" "$d" "$(sudo /lib/udev/scsi_id
--whitelisted --page=$p --device=$d)"; done; done
page 0x80: /dev/sda: 'SATA SMvDi02lGylQfF1qi02lGylQfF1qfjGL9Go6'
page 0x80
The devices don't appear to have the same serial or even the same
product name, I'm unsure why they're be considered as multipathed even
with the apparent same scsi_id as you've discovered.
What does multipath -ll output on this system? Also, could you please
run the following commands:
for d in
Installing this package on the system should not break boot. I think
this is a high-priority bug to fix (including in SRU).
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Medium => High
** Changed in: multipath-
** Changed in: multipath-tools (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1463046
Title:
installation of multipath-tools-boot can
** Bug watch added: Debian Bug tracker #625200
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625200
** Also affects: multipath-tools (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625200
Importance: Unknown
Status: Unknown
--
You received this bug notification b
** Changed in: multipath-tools (Ubuntu)
Status: New => Confirmed
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => Medium
** Description changed:
installing multipath-tools-boot puts multipath code into initramfs.
This code can then cause failure to boot of what woul
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1463046
Title:
installation of multipath-tools-boot can break boot
To manage notifications about this bug
** Attachment added: "lshw output"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1463046/+attachment/4411576/+files/lshw.out
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.la
14 matches
Mail list logo
