Bug 2143125
Summary: | path selector "io-affinity" does not work on RHEL9.2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Lin Li <lilin> |
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 9.2 | CC: | agk, bmarzins, heinzm, msnitzer, prajnoha, zkabelac |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | device-mapper-multipath-0.8.7-16.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-09 08:14:07 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
2022-11-16 05:56:17 UTC
This path selector isn't supported by device-mapper-multipath. It wasn't designed to work with the multipath userspace tools. It requires assigning each path to a specific group of CPUs in a way that doesn't work well with how the multipath tools autodetect paths and autoassemble devices. People who use it create and manage the multipath devices without using the device-mapper-multipath tools. It's inclusion in the man page is an error, and I'll be using this bug to fix that. [root@storageqe-25 ~]# rpm -qa | grep multipath device-mapper-multipath-libs-0.8.7-16.el9.x86_64 device-mapper-multipath-0.8.7-16.el9.x86_64 [root@storageqe-25 ~]# man multipath.conf path_selector The default path selector algorithm to use; they are offered by the kernel multi‐ path target: round-robin 0 Loop through every path in the path group, sending the same amount of I/O to each. Some aspects of behavior can be controlled with the at‐ tributes: rr_min_io, rr_min_io_rq and rr_weight. queue-length 0 (Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on the amount of outstanding I/O to the path. service-time 0 (Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on the amount of outstanding I/O to the path and its relative through‐ put. historical-service-time 0 (Since 5.8 kernel) Choose the path for the next bunch of I/O based on the estimation of future service time based on the history of previous I/O submitted to each path. The default is: service-time 0 Test result: there is no io-affinity in the man page 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 (Moderate: device-mapper-multipath security and bug fix 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/RHSA-2023:2459 |