Bug 1982598

Summary: [power9]multipath.conf has usage typo error for checker_timeout
Product: Red Hat Enterprise Linux 8 Reporter: Lin Li <lilin>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: agk, bmarzins, heinzm, msnitzer, prajnoha, zkabelac
Target Milestone: betaKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.8.4-16.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 19:32:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lin Li 2021-07-15 09:00:53 UTC
Description of problem:
[power9]multipath.conf has usage typo error for checker_timeout

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.8.4-14.el8.ppc64le

How reproducible:
always

Steps to Reproduce:
1.[root@ibm-p9z-20-lp13 ~]# rpm -qa | grep multipath
device-mapper-multipath-libs-0.8.4-14.el8.ppc64le
device-mapper-multipath-0.8.4-14.el8.ppc64le
2.[root@ibm-p9z-20-lp13 ~]# man multipath.conf
       checker_timeout  Specify the timeout to use for path checkers and prioritizers, in sec-
                        onds.  Only prioritizers that issue scsi commands use checker_timeout.
                        Checkers  that  support  an asynchronous mode (tur and directio), will
                        return shortly after being called by multipathd, regardless of whether
                        the  storage  array  responds.  If the storage array hasn't responded,
                        mulitpathd will check for a response every second, until checker_time-
                        out seconds have elapsed.

                        The default is: in /sys/block/sd<x>/device/timeout


Actual results:
mulitpathd will check......

Expected results:
multipathd will check

Additional info:

Comment 1 Lin Li 2021-07-15 09:17:06 UTC
I found the issue on IBM power9 server. But I guess the issue exists all arches.

Comment 2 Ben Marzinski 2021-07-26 16:55:09 UTC
Typo fixed.

Comment 6 Lin Li 2021-07-28 07:21:27 UTC
Verified on device-mapper-multipath-0.8.4-17.el8
[root@ibm-p9z-20-lp13 ~]# rpm -qa | grep multipath
device-mapper-multipath-libs-0.8.4-17.el8.ppc64le
device-mapper-multipath-0.8.4-17.el8.ppc64le

[root@ibm-p9z-20-lp13 ~]# man multipath.conf
     checker_timeout  Specify the timeout to use for path checkers and prior-
                        itizers, in seconds.  Only prioritizers that issue scsi
                        commands  use checker_timeout. Checkers that support an
                        asynchronous  mode  (tur  and  directio),  will  return
                        shortly after being called by multipathd, regardless of
                        whether the storage  array  responds.  If  the  storage
                        array  hasn't  responded,  multipathd  will check for a
                        response every second,  until  checker_timeout  seconds
                        have elapsed.

                        The default is: in /sys/block/sd<x>/device/timeout

Comment 9 errata-xmlrpc 2021-11-09 19:32:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (device-mapper-multipath bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4367