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.
That's odd. Can you try manually loading the path selector modules.
# modprobe dm_service_time
# modprobe dm_round_robin
# modprobe dm_queue_length
Also, can you attach your /etc/multipath.conf and the whole output of
# multipath -v3
when it is failing to load the devices.
Description of problem: Configure XtremIO device in multiapth.conf, the XIO device can't be congnized with "path_selector" attribute. if I remove "path_selector", the XIO device can't be detected. Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.9-65.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. add XtremIO device into multipath.conf device { vendor XtremIO product XtremApp # path_selector "queue-length 0“ path_selector "round-robin 0“ # path_selector "service-time 0“ rr_min_io 1 path_grouping_policy multibus } 2. restart multipath service 3. check multipath device Actual results: XtremIO device can't seen with path_selector Expected results: XtremIO device could be found Additional info: when restart multipath service, the log show =========== XtermIO device is multipathi ======= Mar 18 10:07:10 LXH8SER4 kernel: [15251.285803] device-mapper: table: 253:3: multipath: unknown path selector type Mar 18 10:07:10 LXH8SER4 kernel: [15251.285811] device-mapper: ioctl: error adding target to table Mar 18 10:07:10 LXH8SER4 multipathd: mpathi: removing map Mar 18 10:07:10 LXH8SER4 kernel: device-mapper: table: 253:3: multipath: unknown path selector type Mar 18 10:07:10 LXH8SER4 kernel: device-mapper: ioctl: error adding target to table ================================================== [root@LXh8SER4 ~]# ls -l /dev/mapper/* crw-------. 1 root root 10, 236 Mar 18 05:53 /dev/mapper/control lrwxrwxrwx. 1 root root 7 Mar 18 10:12 /dev/mapper/mpathi -> ../dm-3 ====================================== ls -l //dev/* .... lrwxrwxrwx. 1 root root 7 Mar 18 10:12 253:3 -> ../dm-3