| 2016-05-05 14:19:28 |
Dan Streetman |
bug |
|
|
added bug |
| 2016-05-05 14:19:45 |
Dan Streetman |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-05-05 14:34:27 |
Dan Streetman |
attachment added |
|
lp1578654-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1578654/+attachment/4656460/+files/lp1578654-trusty.debdiff |
|
| 2016-05-05 14:39:08 |
Dan Streetman |
multipath-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-05-05 15:26:00 |
Dan Streetman |
description |
[Impact]
multipath has configuration settings such as "dev_loss_tmo" and "fast_io_fail_tmo" which multipath uses to change the underlying device's parameters. However, it fails to set any of them; it is trying to write the parameters to the sysfs device's directory, instead of the attribute file inside the dir. This results in configuration parameters that the user provides not having any effect at all, and no error logs being shown.
The commit 050b24b33d3c60e29f7820d2fb75e84a9edde528 ("multipath: fix setting sysfs fc timeout parameters") from upstream multipath-tools fixes the bug by actually using the sysfs attribute files, instead of the sysfs device directory.
[Test Case]
A system with either fiberchannel or iSCSI drive(s), with multiple redundant paths to the drive(s), is required. The FC/iSCSI drives must be configured and appear in the system, i.e. as /dev/sd* or similar node that multipath scans.
Check the current value:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
Install multipath-tools, and edit (or create) the /etc/multipath.conf file. Add into the defaults section the setting for fast_io_fail_tmo; if it's already 5, replace 5 shown in the example with a different value than it's currently set to:
defaults {
fast_io_fail_tmo 5
}
If the multipath-tools-boot package is installed, rebuild the initramfs (with update-initramfs -u).
Reboot for the parameter to take effect.
After the system boots back up, multipath should have the drive(s) listed, e.g. in its 'multipath -ll' listing.
Check the sysfs node that should have been modified:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
It should show the value that was configured in multipath.conf.
[Regression Potential]
none. This fixes multipath to correctly set sysfs attributes, as it did not work at all before. |
[Impact]
multipath has configuration settings such as "dev_loss_tmo" and "fast_io_fail_tmo" which multipath uses to change the underlying device's parameters. However, it fails to set any of them; it is trying to write the parameters to the sysfs device's directory, instead of the attribute file inside the dir. This results in configuration parameters that the user provides not having any effect at all, and no error logs being shown.
The commit 050b24b33d3c60e29f7820d2fb75e84a9edde528 ("multipath: fix setting sysfs fc timeout parameters") from upstream multipath-tools fixes the bug by actually using the sysfs attribute files, instead of the sysfs device directory.
[Test Case]
A system with either fiberchannel or iSCSI drive(s), with multiple redundant paths to the drive(s), is required. The FC/iSCSI drives must be configured and appear in the system, i.e. as /dev/sd* or similar node that multipath scans.
Check the current value:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
Install multipath-tools, and edit (or create) the /etc/multipath.conf file. Add into the defaults section the setting for fast_io_fail_tmo; if it's already 5, replace 5 shown in the example with a different value than it's currently set to:
defaults {
fast_io_fail_tmo 5
}
If the multipath-tools-boot package is installed, rebuild the initramfs (with update-initramfs -u).
Reboot for the parameter to take effect.
After the system boots back up, multipath should have the drive(s) listed, e.g. in its 'multipath -ll' listing.
Check the sysfs node that should have been modified:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
It should show the value that was configured in multipath.conf.
[Regression Potential]
none. This fixes multipath to correctly set sysfs attributes, as it did not work at all before. |
|
| 2016-05-05 15:28:29 |
Dan Streetman |
description |
[Impact]
multipath has configuration settings such as "dev_loss_tmo" and "fast_io_fail_tmo" which multipath uses to change the underlying device's parameters. However, it fails to set any of them; it is trying to write the parameters to the sysfs device's directory, instead of the attribute file inside the dir. This results in configuration parameters that the user provides not having any effect at all, and no error logs being shown.
The commit 050b24b33d3c60e29f7820d2fb75e84a9edde528 ("multipath: fix setting sysfs fc timeout parameters") from upstream multipath-tools fixes the bug by actually using the sysfs attribute files, instead of the sysfs device directory.
[Test Case]
A system with either fiberchannel or iSCSI drive(s), with multiple redundant paths to the drive(s), is required. The FC/iSCSI drives must be configured and appear in the system, i.e. as /dev/sd* or similar node that multipath scans.
Check the current value:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
Install multipath-tools, and edit (or create) the /etc/multipath.conf file. Add into the defaults section the setting for fast_io_fail_tmo; if it's already 5, replace 5 shown in the example with a different value than it's currently set to:
defaults {
fast_io_fail_tmo 5
}
If the multipath-tools-boot package is installed, rebuild the initramfs (with update-initramfs -u).
Reboot for the parameter to take effect.
After the system boots back up, multipath should have the drive(s) listed, e.g. in its 'multipath -ll' listing.
Check the sysfs node that should have been modified:
(for iSCSI; replace 'sessionN' with the session number, e.g. 'session1')
# cat /sys/class/iscsi_session/sessionN/
(for FC; replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1')
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
It should show the value that was configured in multipath.conf.
[Regression Potential]
none. This fixes multipath to correctly set sysfs attributes, as it did not work at all before. |
[Impact]
multipath has configuration settings such as "dev_loss_tmo" and "fast_io_fail_tmo" which multipath uses to change the underlying device's parameters. However, it fails to set any of them; it is trying to write the parameters to the sysfs device's directory, instead of the attribute file inside the dir. This results in configuration parameters that the user provides not having any effect at all, and no error logs being shown.
The commit 050b24b33d3c60e29f7820d2fb75e84a9edde528 ("multipath: fix setting sysfs fc timeout parameters") from upstream multipath-tools fixes the bug by actually using the sysfs attribute files, instead of the sysfs device directory.
[Test Case]
A trusty system with fiberchannel drive(s), with multiple redundant paths to the drive(s), is required. The FC drives must be configured and appear in the system, i.e. as /dev/sd* or similar node that multipath scans.
Note that multipath-tools in trusty does not (yet) support setting sysfs attributes for iSCSI devices, only FC.
Check the current value, replace 'rport-N:N-N' with the rport number, e.g. 'rport-0:0-1':
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
Install multipath-tools, and edit (or create) the /etc/multipath.conf file. Add into the defaults section the setting for fast_io_fail_tmo; if it's already 5, replace 5 shown in the example with a different value than it's currently set to:
defaults {
fast_io_fail_tmo 5
}
If the multipath-tools-boot package is installed, rebuild the initramfs (with update-initramfs -u).
Reboot for the parameter to take effect.
After the system boots back up, multipath should have the drive(s) listed, e.g. in its 'multipath -ll' listing.
Check the sysfs node that should have been modified (again replace rport-* with the correct numbers):
# cat /sys/class/fc_remote_ports/rport-N:N-N/fast_io_fail_tmo
It should show the value that was configured in multipath.conf.
[Regression Potential]
none. This fixes multipath to correctly set sysfs attributes, as it did not work at all before. |
|
| 2016-05-05 15:28:44 |
Dan Streetman |
summary |
multipath does not set sysfs params correctly |
multipath does not set fiberchannel params correctly |
|
| 2016-05-11 18:08:10 |
Chris J Arges |
bug task added |
|
multipath-tools (Ubuntu Trusty) |
|
| 2016-05-11 18:27:39 |
Dan Streetman |
multipath-tools (Ubuntu Trusty): assignee |
|
Dan Streetman (ddstreet) |
|
| 2016-05-11 18:27:43 |
Dan Streetman |
multipath-tools (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2016-05-11 18:28:05 |
Dan Streetman |
multipath-tools (Ubuntu Trusty): status |
New |
In Progress |
|
| 2016-05-17 18:48:57 |
Dan Streetman |
attachment added |
|
lp1578654-trusty-v2.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/multipath-tools/+bug/1578654/+attachment/4664865/+files/lp1578654-trusty-v2.debdiff |
|
| 2016-05-20 15:26:47 |
Louis Bouchard |
tags |
sts |
sts sts-sponsor |
|
| 2016-05-25 11:26:59 |
Dan Streetman |
attachment added |
|
lp1578654-trusty-v3.debdiff https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1578654/+attachment/4670099/+files/lp1578654-trusty-v3.debdiff |
|
| 2016-06-07 15:36:54 |
Louis Bouchard |
tags |
sts sts-sponsor |
sts sts-sponsor sts-sru |
|
| 2016-06-08 16:55:01 |
Chris J Arges |
multipath-tools (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2016-06-08 16:55:03 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-06-08 16:55:05 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2016-06-08 16:55:09 |
Chris J Arges |
tags |
sts sts-sponsor sts-sru |
sts sts-sponsor sts-sru verification-needed |
|
| 2016-06-09 21:13:41 |
Dan Streetman |
tags |
sts sts-sponsor sts-sru verification-needed |
sts sts-sponsor sts-sru verification-done |
|
| 2016-06-16 16:02:21 |
Launchpad Janitor |
multipath-tools (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2016-06-16 16:02:26 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-06-22 16:53:20 |
Louis Bouchard |
tags |
sts sts-sponsor sts-sru verification-done |
sts sts-sru verification-done |
|
| 2016-11-09 12:21:49 |
Louis Bouchard |
tags |
sts sts-sru verification-done |
sts verification-done |
|
