Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: "queue_mode mq" did not show in the output of "multipath -ll" when use_blk_mq and multipath.conf set properly. Version-Release number of selected component (if applicable): [root@localhost ] cat /proc/version Linux version 4.18.0-80.el8.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 8.2.1 20180905 (Red Hat 8.2.1-3) (GCC)) #1 SMP Wed Mar 13 12:02:46 UTC 2019 [root@localhost ]# rpm -qa | grep device-mapper device-mapper-multipath-0.7.8-7.el8.x86_64 device-mapper-event-1.02.155-6.el8.x86_64 device-mapper-libs-1.02.155-6.el8.x86_64 device-mapper-multipath-libs-0.7.8-7.el8.x86_64 device-mapper-persistent-data-0.7.6-1.el8.x86_64 device-mapper-event-libs-1.02.155-6.el8.x86_64 device-mapper-1.02.155-6.el8.x86_64 How reproducible: Easy to reproduce. Steps to Reproduce: 1. Install RHEL8, 2. Zone and configure a nvme device to this host, 3, configure multipath.conf, 4, multipath -ll 5, check if the output has "queue_mode mq" [root@localhost ]cat /sys/module/scsi_mod/parameters/use_blk_mq Y [root@localhost ]# cat /sys/module/dm_mod/parameters/use_blk_mq Y [root@localhost ]# cat /etc/multipath.conf ################################################################## # multipath.conf - generated by setup_host_multipath.pl # The multipath.conf configuration file has been updated. # the original configuration file was copied to /etc/multipath.conf.<TIME>.backup # devices { device { vendor "NVME" product "IBM\s+2145" path_grouping_policy "multibus" path_selector "round-robin 0" prio "const" path_checker "none" failback "immediate" no_path_retry "queue" rr_weight uniform rr_min_io_rq "1" fast_io_fail_tmo 15 dev_loss_tmo 600 } device { vendor "IBM" product "2145" path_grouping_policy "group_by_prio" path_selector "service-time 0" prio "alua" path_checker "tur" failback "immediate" no_path_retry 5 rr_weight uniform rr_min_io_rq "1" dev_loss_tmo 120 } } defaults { user_friendly_names yes path_grouping_policy group_by_prio } Actual results: no "queue_mode mq" mpathal (eui.c0000000000000200050760810ca0166) dm-7 NVME,IBM 2145 size=1.0G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active `- 0:161:5:5 nvme0n5 259:4 active ready running Expected results: has "queue_mode mq" linux-u9qs:~ # multipath -ll mpathd (eui.c00000000000002c0050760810ca0166) dm-2 NVME,IBM 2145 size=1.0G features='3 queue_if_no_path queue_mode mq' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=enabled |- 0:161:1:17 nvme0n1 259:0 active ready running `- 1:112:1:17 nvme1n1 259:1 active ready running Additional info: not yet.