Bug 2053642

RHEL-9 packages with this fix are available for testing at:

http://people.redhat.com/~bmarzins/device-mapper-multipath/rpms/RHEL9/2053642/

Muneendra, It would be really helpful for getting this into RHEL-9.0 if you could test these before the end of next week.

Muneendra, just a ping to remind you that it would be very helpful to get this tested before the end of this week.

Hi Benjamin,
I have installed the packages and tested the same on top of RHEL9 Beta.
We have injected the FPIN from the switch while the host is running the traffic.
On the host the affected paths and port_states have  been marked as marginal and the traffic has been shifted to active paths.
And things are working fine as expected.
With this testing we can conclude that the packages which you have sent are working fine.
And it is good to go.

Move to verified according to comment 10 and comment 12.

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 (new packages: device-mapper-multipath), 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-2022:3971

# man multipath.conf
defaults section 
     marginal_pathgroups
                        If set to off, the delay_*_checks, marginal_path_*, and san_path_err_* options will keep
                        marginal, or "shaky", paths from being reinstated until they  have  been  monitored  for
                        some time. This can cause situations where all non-marginal paths are down, and no paths
                        are usable until multipathd detects this and reinstates a marginal path. If  the  multi‐
                        path device is not configured to queue IO in this case, it can cause IO errors to occur,
                        even though there are marginal paths available.  However, if this option is set  to  on,
                        when  one  of the marginal path detecting methods determines that a path is marginal, it
                        will be reinstated and placed in a seperate pathgroup that will only be used  after  all
                        the  non-marginal  pathgroups have been tried first. This prevents the possibility of IO
                        errors occuring while marginal paths are still usable. After the path has been monitored
                        for  the  configured  time,  and  is declared healthy, it will be returned to its normal
                        pathgroup.  If this option is set to fpin, multipathd will receive  fpin  notifications,
                        set  path  states to "marginal" accordingly, and regroup paths as described for on. This
                        option can't be used in combination with other options for "Shaky path  detection"  (see
                        below). Note: If this is set to fpin, the marginal_path_* and san_path_err_* options are
                        implicitly set to no. Also, this option cannot be switched either to or from fpin  on  a
                        multipathd reconfigure. multipathd must be restarted for the change to take effect.  See
                        "Shaky paths detection" below for more information.

                        The default is: off


# cat /etc/multipath.conf
defaults {
	user_friendly_names yes
	find_multipaths yes
        marginal_pathgroups fpin
}


# multipathd show config
defaults {
	marginal_pathgroups "off"