Hi @toreanderson,
The not relevant statement is not at you :) just explaining why I didn't
verify on vivid.
I've seen some reports that this functionality is no longer working on
Trusty too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Ok, so I found the bug. The problematic code is in
sysfs_attr_set_value() in libmultipath/sysfs.c:
devpath = udev_device_get_syspath(dev);
condlog(4, "open '%s'/'%s'", devpath, attr_name);
if (stat(devpath, ) != 0) {
condlog(4, "stat '%s' failed: %s",
Okay, sorry about the irrelevant verification on Vivid then. But I'd
like to point out that Trusty behaves exactly the same, i.e., the bug is
*not* fixed. Using the exact same multipath.conf as I mentioned in
comment #31 with multipath-tools on 0.4.9-3ubuntu7.9, I get the exact
same behaviour.
I tested it on Vivid, and it does not work. The dev_loss_tmo and
fast_io_fail_tmo sysfs settings do *not* get set. More information on my
test environment below:
root@ucstest:~# cat /etc/multipath.conf
defaults {
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
devices
device {
vendor "HP.*"
The verification for vivid is no longer relevant as it's EOL by Feb,
2016. Thanks.
--
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/1435706
Title:
DevLossTO, FastIoFailTO
Can https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu12.15.04.1 be verified for vivid as well? Thanks!
--
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/1435706
Hi,
The re-verification of this shows it's indeed fixed with multipath-tools
0.4.9-3ubuntu7.4.
Details provided.
Software version check:
# lsb_release -d
Description:Ubuntu 14.04.3 LTS
# dpkg -s multipath-tools | grep ^Version:
Version: 0.4.9-3ubuntu7.4
Sigh; ignore bugproxy again.
There are no new patches here.
--
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/1435706
Title:
DevLossTO, FastIoFailTO settings do not match
Ok, so I did some more testing. It appears that the problem isn't
specific to the dev_loss_tmo and fast_io_fail_tmo setting. This is
evidenced by the terminal log below. In multipath.conf (which we know
for certain is being read, as the created multipath map gets the correct
alias), I instruct it
Is it possible that the issue might be something else that is directly
related to the devices themselves rather than the behavior in multipath-
tools?
I haven't looked very far yet, but maybe we're missing some other
commit, too.
** Tags removed: verification-needed
** Changed in:
I verified that this bug is *NOT* fixed by trying the exact identical
configuration (which is as minimal as possible) both with Ubuntu Trusty
and with Scientific Linux 6 (RHEL6 clone). The test machine is a Cisco
B200M2 blade server, using the Cisco VIC FCoE HBA (fnic.ko driver). The
storage array
** 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
Reopening the Trusty task based on
https://bugs.launchpad.net/ubuntu/+source/multipath-
tools/+bug/1468897/comments/15 and comment #17 from this bug, which
suggests this fix isn't complete.
** Changed in: multipath-tools (Ubuntu Trusty)
Status: Fix Released = Triaged
** Tags removed:
To me fix doesn't actually appear to work. After upgrading to multipath-
tools 0.4.9-3ubuntu7.4on an amd64 trusty and rebooting, the
fast_io_fail_tmo and dev_loss_tmo values do not get written to sysfs:
$ grep . /sys/class/fc_remote_ports/*/*_tmo
This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu7.4
---
multipath-tools (0.4.9-3ubuntu7.4) trusty; urgency=medium
* Remove 0024-ignore-usb.patch: Ignore USB devices. Verification fails
for this fix; it needs more work.
multipath-tools (0.4.9-3ubuntu7.3)
Hi,
I don't have the hardware to verify this quickly handy now, but I verified the
interdiff between what's in trusty-proposed and the debdiff I submitted in
comment #8 and verified in comment #9 for the 0020-0023 patches, and changes
are only in diff headers and hunks' @@ function strings.
** Branch linked: lp:~mathieu-tl/ubuntu/trusty/multipath-tools/usb+local
--
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/1435706
Title:
DevLossTO, FastIoFailTO settings do
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14043
--
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/1435706
Title:
DevLossTO, FastIoFailTO
Hello bugproxy, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
+ [Impact]
+ This bug impacts multipath users who need to tweak timeout values for DevLoss
and FastIoFail for performance reasons.
+
+ [Test Case]
+ On a multipath system, attempt to modify DevLossTO or FastIoFailTO, then
verify that the values got applied with
** 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/1435706
Title:
DevLossTO,
Digging deeper, looks like the DevLossTO and FastIoFailTO settings fixes
are already in 0.5.0; so the changes are in wily.
Moving on to SRU this to vivid, trusty.
** Changed in: multipath-tools (Ubuntu)
Status: In Progress = Fix Released
** Changed in: multipath-tools (Ubuntu Vivid)
** Also affects: multipath-tools (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = In Progress
** Changed in: multipath-tools (Ubuntu Vivid)
Status: New = Confirmed
** Changed in: multipath-tools (Ubuntu Vivid)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: multipath-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Tags removed: architecture-ppc64
** Tags added: architecture-ppc64le
--
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/1435706
Title:
DevLossTO, FastIoFailTO settings do
** Package changed: ubuntu = multipath-tools (Ubuntu)
--
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/1435706
Title:
DevLossTO, FastIoFailTO settings do not match
26 matches
Mail list logo
