[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1435706 Title: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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", devpath, strerror(errno));
return 0;
}
/* skip directories */
if (S_ISDIR(statbuf.st_mode))
return 0;
The problem here is that stat() gets called on the containing directory
in devpath (as opposed to devpath+attr_name). Then the code proceeds to
check if that is a directory (which obviously it is going to be) and
before returning without having done anything. The rest of the function
also seems to assume that "devpath" contains the full path to the sysfs
attribute as opposed to the containing directory.
How the verification in comment #22 could have found this code to be
working is beyond me, as the only place where the attr_name variable is
actively being used for anything in the function is in the condlog()
call.
It appears this got fixed upstream by
http://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=050b24b33d3c60e29f7820d2fb75e84a9edde528 . This
patch applies fine to the multipath-tools 0.4.9-3ubuntu7.9 sources from
trusty (with --fuzz=3), and I can confirm that it does fix the problem
for me - the sysfs timeout attributes gets set correctly when the maps
is being created (both when using multipathd and the multipath tool).
Tore
--
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 multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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. That is, it is apparent that multipathd does read the settings from the config file (as they're visible in output from "multipathd -k'show config'"), but they're not being applied/written to sysfs. If I run use the command line utility in verbose mode to create the map, it does claim that it opens the sysfs files in question, but strace shows no sign of that actually happening: root@ucstest:~# /etc/init.d/multipath-tools stop * Stopping multipath daemon multipathd [ OK ] root@ucstest:~# multipath -F root@ucstest:~# strace -ff -eopen multipath -v4 |& egrep 'create:|_tmo' Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: fast_io_fail_tmo = 16 (controller default) Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: dev_loss_tmo = 2048 (controller default) Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-1/fc_remote_ports/rport-1:0-1'/'dev_loss_tmo' ort-1:0-1'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'fast_io_fail_tmo' create: 3600c0ff0001204a9d12b75510100 undef HP ,P2000G3 FC/iSCSI Note that this is a lab system, so if you'd like, you can have a look yourself, Mathieu. Just send me a SSH pubkey on IRC and I'll set up a user account for you. Tore -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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.*"
product "P2000G3.*"
path_grouping_policy "multibus"
fast_io_fail_tmo 16
dev_loss_tmo 2048
}
}
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:1 sdb 8:16 active ready running
|- 1:0:1:1 sdc 8:32 active ready running
|- 2:0:0:1 sdd 8:48 active ready running
`- 2:0:1:1 sde 8:64 active ready running
I know for a fact that the device{} section is being applied, because if
I remove the path_grouping_policy keyword and restart multipathd, the
topology changes to one path per group:
root@ucstest:~# sed -i 's/path_grouping/#path_grouping/' /etc/multipath.conf
root@ucstest:~# systemctl restart multipath-tools.service
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:1:1 sdc 8:32 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:0:1 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 2:0:1:1 sde 8:64 active ready running
After reverting that change and restarting again, I can confirm that my
config file timeout settings are being read by multipathd:
root@ucstest:~# multipathd -k'show config' | grep -B5 -A1 dev_loss_tmo
defaults {
verbosity 2
wwids_file /etc/multipath/wwids
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
--
device {
vendor "HP.*"
product "P2000G3.*"
path_grouping_policy multibus
fast_io_fail_tmo 16
dev_loss_tmo 2048
}
However, they are *not* being applied to sysfs:
root@ucstest:~# grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-2/fast_io_fail_tmo:off
Versions:
root@ucstest:~# dpkg -l kpartx multipath-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
ArchitectureDescription
+++-=-===-===-
ii kpartx
0.4.9-3ubuntu12.15.04.2 amd64 create device
mappings for partitions
ii multipath-tools
0.4.9-3ubuntu12.15.04.2 amd64 maintain
multipath block device access
Tore
--
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 multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 Title: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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
Set known values to the fast_io_fail_tmo (21) and dev_loss_tmo (42) files,
and activate multipathd to re-set the values according to its configuration.
# /etc/init.d/multipath-tools stop
* Stopping multipath daemon multipathd
...done.
# for fastiofail in
/sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo; do echo 21 > $fastiofail;
done
# grep -h . /sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo | sort
-u
21
# for devloss in /sys/class/fc_remote_ports/rport-*/dev_loss_tmo; do
echo 42 > $devloss; done
# grep -h . /sys/class/fc_remote_ports/rport-*/dev_loss_tmo | sort -u
42
# /etc/init.d/multipath-tools start
* Starting multipath daemon multipathd
...done.
The storage products used:
# multipath -l | grep ^mpath | cut -d, -f2 | sort -u
2107900
2145
2810XIV
FlashSystem-9840
The active configuration for them:
# multipathd -k'show config' | grep '{\|}\|product\|tmo'
defaults {
fast_io_fail_tmo 10
}
...
devices {
...
device {
product "2107900"
}
device {
product "2145"
dev_loss_tmo 120
}
...
device {
product "2810XIV"
}
device {
product "FlashSystem-9840"
fast_io_fail_tmo 25
dev_loss_tmo 300
}
}
...
The active configuration is sysfs:
The sysfs setting (see below) are all set correctly,
according to the multipath configuration (above).
On rports to 2107900 or 2810XIV, devloss = 42 (not specified; system)
and fastiofail = 10 (defaults).
On rports to 2145, devloss = 120 (device), fastiofail = 10 (defaults).
On rports to 9840, devloss = 300 (product) and fastiofail = 25
(product).
On rports not connected to any of those, the system/known values
are left unchanged.
# grep .
/sys/class/fc_remote_ports/rport-*/{dev_loss_tmo,fast_io_fail_tmo,device/target*/*/model}
| sort -V
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:21
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:21
/sys/class/fc_remote_ports/rport-1:0-2/device/target1:0:0/1:0:0:0/model:2810XIV-LUN-0
/sys/class/fc_remote_ports/rport-1:0-2/device/target1:0:0/1:0:0:1/model:2810XIV
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:10
/sys/class/fc_remote_ports/rport-1:0-3/device/target1:0:1/1:0:1:0/model:2145
/sys/class/fc_remote_ports/rport-1:0-3/dev_loss_tmo:120
/sys/class/fc_remote_ports/rport-1:0-3/fast_io_fail_tmo:10
/sys/class/fc_remote_ports/rport-1:0-4/device/target1:0:2/1:0:2:0/model:FlashSystem-9840
/sys/class/fc_remote_ports/rport-1:0-4/dev_loss_tmo:300
/sys/class/fc_remote_ports/rport-1:0-4/fast_io_fail_tmo:25
/sys/class/fc_remote_ports/rport-1:0-5/device/target1:0:3/1:0:3:0/model:2107900
/sys/class/fc_remote_ports/rport-1:0-5/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-5/fast_io_fail_tmo:10
/sys/class/fc_remote_ports/rport-1:0-6/device/target1:0:4/1:0:4:0/model:2145
/sys/class/fc_remote_ports/rport-1:0-6/dev_loss_tmo:120
/sys/class/fc_remote_ports/rport-1:0-6/fast_io_fail_tmo:10
/sys/class/fc_remote_ports/rport-1:0-7/device/target1:0:5/1:0:5:0/model:FlashSystem-9840
/sys/class/fc_remote_ports/rport-1:0-7/dev_loss_tmo:300
/sys/class/fc_remote_ports/rport-1:0-7/fast_io_fail_tmo:25
/sys/class/fc_remote_ports/rport-1:0-8/device/target1:0:6/1:0:6:0/model:2810XIV-LUN-0
/sys/class/fc_remote_ports/rport-1:0-8/device/target1:0:6/1:0:6:1/model:2810XIV
/sys/class/fc_remote_ports/rport-1:0-8/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-8/fast_io_fail_tmo:10
/sys/class/fc_remote_ports/rport-1:0-9/device/target1:0:7/1:0:7:0/model:2810XIV-LUN-0
/sys/class/fc_remote_ports/rport-1:0-9/device/target1:0:7/1:0:7:1/model:2810XIV
/sys/class/fc_remote_ports/rport-1:0-9/dev_loss_tmo:42
/sys/class/fc_remote_ports/rport-1:0-9/fast_io_fail_tmo:10
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 to use the ALUA hardware handler for all devices.
However, for some reason, this is ignored, and the EMC hardware handler
is used instead:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor .*
product .*
hardware_handler 1 alua
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
This does *NOT* happen on RHEL-based distros - on those, changing the
hardware_handler in multipath.conf in this way works as expected.
So why does it use the EMC hardware_handler? Well, there's a built-in
default device section that matches the array in question. So this
appears to override my user-specified config from multipath.conf:
=
root@ucstest-osl2:~# multipathd -k'show config' | grep -B10 -A4 '1 emc'
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 emc
prio emc
failback immediate
no_path_retry 60
}
=
If I copy the entire default device config into /etc/multipath.conf and
only change the hardware_handler setting, then it starts working:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 alua
prio emc
failback immediate
no_path_retry 60
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
It would appear that for some reason, in order to override default
device settings in Ubuntu there must be an *exact* string match between
the user-supplied «vendor» and «product» settings. If I change e.g.
«product» in multipath.conf to .*.*, then it starts using the built-in
defaults again, ignoring multipath.conf. I consider this behaviour very
dangerous - consider that if the admin has a working config (due to
exact matching vendor/product settings), and then the package gets
updated and extends the built-in defaults to incorporate some new model
matching the same profile/settings). At this point the admin's working
config will stop being used, possibly causing disruptive problems. I
therefore strongly suggest you figure out why it behaves differently in
Ubuntu and RHEL, and adopt the RHEL behaviour which really is the only
sensible one.
In any case, now that I know how to ensure my multipath.conf settings
are being used, I re-tried adding dev_loss_tmo and fast_io_fail_tmo, but
it still doesn't work:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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: multipath-tools (Ubuntu Vivid) Status: Fix Committed = Triaged -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 is an EMC VNX5300, which is reached via FCoE (inside the
Cisco UCS infrastructure) and then traditional FC fabric.
The following console output is taken with Trusty installed. Note that
it was fully upgraded. After creating /etc/multipath.conf with the
indicated contents, update-initramfs was run and the system rebooted,
just to make sure the settings had taken effect. As you can see from the
output, the dev_loss_tmo and fast_io_fail_tmo settings are *NOT*
applied:
=-=-=-=-=-=-=-=
tore@ucstest-osl2:~$ cat /etc/multipath.conf
devices {
device {
vendor .*
product .*
fast_io_fail_tmo3
dev_loss_tmo2147483647
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
tore@ucstest-osl2:~$ sudo multipath -ll
bootvolume (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| |- 0:0:1:0 sdb 8:16 active ready running
| `- 1:0:1:0 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 1:0:0:0 sdc 8:32 active ready running
`- 0:0:0:0 sda 8:0 active ready running
tore@ucstest-osl2:~$ grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-0:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-0:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-0:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
tore@ucstest-osl2:~$ uname -r
3.13.0-62-generic
tore@ucstest-osl2:~$ md5sum /etc/multipath.conf
27a62898e80a0bcd7e62b5f2e8d675ff /etc/multipath.conf
tore@ucstest-osl2:~$ echo 3 | sudo tee
/sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo
3
tore@ucstest-osl2:~$ echo 2147483647 | sudo tee
/sys/class/fc_remote_ports/rport-*/dev_loss_tmo
2147483647
tore@ucstest-osl2:~$ grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-0:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-0:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-0:0-2/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-2/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:3
tore@ucstest-osl2:~$ dpkg -l multipath-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==---=
ii multipath-tools0.4.9-3ubuntu7.4 amd64
maintain multipath block
=-=-=-=-=-=-=-=
This shows the exact same multipath.conf file being used on SL6, and in
this case the sysfs settings *ARE* applied when the multipath map is
registered (no reboot required):
=-=-=-=-=-=-=-=
[root@ucstest-osl2 ~]# uname -r
2.6.32-358.23.2.el6.x86_64
[root@ucstest-osl2 ~]# rpm -qa device-mapper-multipath
device-mapper-multipath-0.4.9-80.el6.x86_64
[root@ucstest-osl2 ~]# grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1435706 Title: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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: verification-done ** Tags added: verification-needed -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:off
The device stanza from multipath.conf contains the following:
device {
vendor DGC|EMC
product RAID [0-9]*|VRAID|SYMMETRIX.*
path_grouping_policygroup_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checkeremc_clariion
features0
hardware_handler1 emc
prioemc
failbackimmediate
rr_weight uniform
no_path_retry queue
rr_min_io 100
fast_io_fail_tmo3
dev_loss_tmo2147483647
}
FWIW, I can manually set the sysfs settings to the desired values:
$ echo 3 | sudo tee /sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo
3
$ echo 2147483647 | sudo tee /sys/class/fc_remote_ports/rport-*/dev_loss_tmo
2147483647
$ grep . /sys/class/fc_remote_ports/*/*_tmo
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:3
Tore
--
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 multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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) trusty; urgency=medium * Added debian/patches/0015-shared-lock-for-udev.patch (LP: #1431650) * Support disks with non 512-byte sectors (LP: #1441930) * Correctly write FC timeout attributes to sysfs. (LP: #1435706) * Ignore USB devices. (LP: #1468897) -- Mathieu Trudel-Lapierre mathieu...@ubuntu.com Mon, 27 Jul 2015 13:48:39 -0400 ** Changed in: multipath-tools (Ubuntu Trusty) Status: Fix Committed = Fix Released -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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. Looks good. If a report on the real thing is really required, just let me know. ** Tags removed: verification-needed ** Tags added: verification-done -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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 package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: multipath-tools (Ubuntu Trusty) Status: Confirmed = Fix Committed ** Tags added: verification-needed ** Changed in: multipath-tools (Ubuntu Vivid) Status: In Progress = Fix Committed -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 'multipath -l'. See below. + + [Regression Potential] + Users who have already modified these values but have not noticed they did not properly apply may notice a change in behavior on device failure. + + --- + Problem Description = DevLossTO, FastIoFailTO settings do not match multipath.conf expected values ---uname output--- Linux ilp1fc85apA4.tuc.stglabs.ibm.com 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 ppc64le ppc64le ppc64le GNU/Linuxuname -m - - Machine Type = p7 8247 - + + Machine Type = p7 8247 + Steps to Reproduce === - Verify DevLossTO, FastIoFailTO setting match multipath.conf expected values - + Verify DevLossTO, FastIoFailTO setting match multipath.conf expected values + == Comment: #31 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com - 2015-03-20 10:57:20 == OK. From the point of view of multipathd, everything seems correct, by looking at the logs. I even parsed syslog and the output of getHBAInfo in order to find inconsistencies, and the inconsistency is between what multipathd logged as configured for a given target, and what its rport reports at getHBAInfo. So, either multipathd is not configuring the timeouts even though it has the right configuration, or something else is changing those timeouts. The other problem is that multipathd does not include the dev_loss_tmo configuration for 2145 as can be seen from list config. So, it could be not parsing the configuration correctly, or there could be a problem with the configuration. At this point, to move forward, I would like to take a look at your system, and try reconfigure and looking at some strace output of multipathd, to check for writes into sysfs. - == Comment: #34 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com - 2015-03-20 15:56:46 == OK, so I investigated in the system and read some of the code and checked changelog. It looks like Ubuntu is shipping a fairly old version of multipath- tools, which is understandable, since multipath-tools is not very good in doing frequent releases, so one needs to either ship a version closer to upstream git or include its own large set of patches. One of the patches missing is the one attached next. Without that, any devices included in the built-in hardware table will have some of its attributes from the config file ignored. That is the case with 2145. So, we lose the dev_loss_tmo setting for that device. Cascardo. == Comment: #38 - Thadeu Lima De Souza Cascardo thad...@br.ibm.com - 2015-03-20 16:25:39 == The bug this patch fixes would explain why fast_io_fail_tmo is not correctly set in some cases, but not dev_loss_tmo. So, probably, there is another missing patch here. I would like to experiment with the two patches I mentioned, however. Let's try to do this on Monday? Cascardo. -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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) Status: Confirmed = In Progress -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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) Importance: Undecided = Medium ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = Medium ** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Changed in: multipath-tools (Ubuntu Vivid) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Also affects: multipath-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: multipath-tools (Ubuntu Trusty) Status: New = Confirmed ** Changed in: multipath-tools (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: multipath-tools (Ubuntu Trusty) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
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. https://bugs.launchpad.net/bugs/1435706 Title: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
** 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 multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
