RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2065477 - [RFE] enable device configuration selection to include the transport protocol.
Summary: [RFE] enable device configuration selection to include the transport protocol.
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: device-mapper-multipath
Version: 8.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Lin Li
Renata Harcarikova
Depends On:
Blocks: 2084365
TreeView+ depends on / blocked
Reported: 2022-03-17 23:12 UTC by Lance Digby
Modified: 2022-11-08 12:31 UTC (History)
10 users (show)

Fixed In Version: device-mapper-multipath-0.8.4-24.el8
Doc Type: Enhancement
Doc Text:
.`multipath.conf` can now include protocol-specific configuration overrides in DM Multipath You can access paths of multipath devices through various protocols. Because various protocols can have various optimal configurations, it was previously not possible to set the optimal configuration for all protocols in the Device Mapper Multipath feature without a per-protocol option. With this enhancement, you can include protocol-specific configuration overrides in the `multipath.conf` file. As a result, you can now configure multipath device paths on a per-protocol basis, allowing for the correct configuration of multipath devices accessible through multiple protocols.
Clone Of:
: 2084365 (view as bug list)
Last Closed: 2022-11-08 10:47:39 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-116039 0 None None None 2022-03-17 23:16:12 UTC
Red Hat Product Errata RHBA-2022:7714 0 None None None 2022-11-08 10:48:19 UTC

Comment 4 Ben Marzinski 2022-05-17 18:28:02 UTC
The final solution to to is to add a protocol subsection to the overrides section of multipath.conf, which can contain multiple protocol subsections. Path devices are matched against the protocol subsection using the mandatory "type" attribute.  Attributes in a matching protocol subsection take precedence over attributes in the rest
of the overrides section, which like always take precedence of attributes in the devices and defaults sections. If there are multiple matching protocol subsections, later entries take precedence. The "type" attribute can be one of scsi:fcp, scsi:spi, scsi:ssa, scsi:sbp, scsi:srp, scsi:iscsi, scsi:sas, scsi:adt, scsi:ata, scsi:unspec, ccw, cciss, nvme, and undef. The protocol that a path is using can be viewed by running:

multipathd show paths format "%d %P"

The only attributes that can be set in the protocol subsection are "type", "dev_loss_tmo", "fast_io_fail_tmo", and "eh_deadline". Here is an example of a overrides sections with protocol subsections:

overrides {
        protocol {
                type "scsi:fcp"
                dev_loss_tmo 70
                fast_io_fail_tmo 10
                eh_deadline 360
        protocol {
                type "scsi:iscsi"
                fast_io_fail 120

Comment 16 errata-xmlrpc 2022-11-08 10:47:39 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.


Note You need to log in before you can comment on or make changes to this bug.