Red Hat Bugzilla – Bug 1482629
Please add TUR path checker to default hardware table for Nimble devices
Last modified: 2018-04-10 12:14:07 EDT
Description of problem: path_checker option is missing in default hardware table for Nimble and by default "directio" is selected. Nimble is a active/standby array and directio commands fails on stand-by paths. Please add path_checker "tur" to Nimble device table. current settings:(missing path_checker) { vendor "Nimble" product "Server" path_grouping_policy "group_by_prio" path_selector "round-robin 0" features "1 queue_if_no_path" hardware_handler "1 alua" prio "alua" failback immediate fast_io_fail_tmo 1 dev_loss_tmo "infinity" } Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.9-111.el7.x86_64 device-mapper-multipath-libs-0.4.9-111.el7.x86_64 How reproducible: consistent Steps to Reproduce: 1. Install or Upgrade to RHEL 7.4 2. Run multipath -ll 3. All stand-by paths appear as failed/faulty devices Actual results: Paths appear as failed/faulty instead of ghost. Expected results: stand-by paths should appear as active/ghost instead of failed/faulty Additional info: [root@rtp-iron-ops06 ~]# multipath -ll mpatha (29b67c5b1833be9dd6c9ce90038a5a0c6) dm-0 Nimble ,Server size=150G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='round-robin 0' prio=50 status=active |- 7:0:2:0 sdg 8:96 failed faulty running |- 8:0:1:0 sdb 8:16 failed faulty running |- 7:0:3:0 sdh 8:112 failed faulty running |- 8:0:2:0 sdc 8:32 failed faulty running |- 7:0:0:0 sde 8:64 active ready running |- 8:0:0:0 sda 8:0 active ready running |- 7:0:1:0 sdf 8:80 active ready running `- 8:0:3:0 sdd 8:48 active ready running Aug 17 14:16:48 rtp-iron-ops06 multipathd: mpatha: sdc - directio checker reports path is down Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:2:0: [sdg] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:2:0: [sdg] tag#0 Sense Key : Not Ready [current] Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:2:0: [sdg] tag#0 Add. Sense: Logical unit not accessible, target port in standby state Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:2:0: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 Aug 17 14:16:48 rtp-iron-ops06 kernel: blk_update_request: I/O error, dev sdg, sector 0 Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:3:0: [sdh] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:3:0: [sdh] tag#1 Sense Key : Not Ready [current] Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:3:0: [sdh] tag#1 Add. Sense: Logical unit not accessible, target port in standby state Aug 17 14:16:48 rtp-iron-ops06 kernel: sd 7:0:3:0: [sdh] tag#1 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 Aug 17 14:16:48 rtp-iron-ops06 kernel: blk_update_request: I/O error, dev sdh, sector 0 Aug 17 14:16:49 rtp-iron-ops06 multipathd: mpatha: sdg - directio checker reports path is down Aug 17 14:16:49 rtp-iron-ops06 multipathd: mpatha: sdh - directio checker reports path is down Aug 17 14:16:49 rtp-iron-ops06 kernel: sd 8:0:1:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Aug 17 14:16:49 rtp-iron-ops06 kernel: sd 8:0:1:0: [sdb] tag#0 Sense Key : Not Ready [current] Aug 17 14:16:49 rtp-iron-ops06 kernel: sd 8:0:1:0: [sdb] tag#0 Add. Sense: Logical unit not accessible, target port in standby state Aug 17 14:16:49 rtp-iron-ops06 kernel: sd 8:0:1:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Hi, Any update on this and can you let us know the timeline when next device-mapper-multipath update is available?
Are you just looking for a build to test? The next official build will be rhel-7.5.
Is it possible to push this to Errata updates for device-mapper-multipath before RHEL 7.5?
It would have to go out as a z-stream fix. I'm not able to decide this myself. That's a product management decision.
Please let us know how we(hpe) can help to consider this for z-stream. Without this fix, our inbuilt device table is useless and customers still have to perform manual configuration. Also, are you planning to post this patch upstream with other patches or do you want me to create one? Thanks.
Any update on when this will be included?
Hi Ben, Can you please provide the timeline of when this will be updated? Also, are you planning to post this patch upstream or do you want me to post one. Please let me know. Thanks.
Added TUR checker to builtin config.
Thanks Ben.
Hello shivamerla1, Because we don't have Nimble storage, we can only check default configuration. Could you help check if it works normally for you? Thanks in advance.
Reproduced on device-mapper-multipath-0.4.9-111 1, # rpm -qa | grep multipath device-mapper-multipath-libs-0.4.9-111.el7.x86_64 device-mapper-multipath-0.4.9-111.el7.x86_64 2, # multipathd show config device { vendor "Nimble" product "Server" path_grouping_policy "group_by_prio" path_selector "round-robin 0" features "1 queue_if_no_path" hardware_handler "1 alua" prio "alua" failback immediate fast_io_fail_tmo 1 dev_loss_tmo "infinity" } Verified on device-mapper-multipath-0.4.9-116.el7 1, # rpm -qa | grep multipath device-mapper-multipath-libs-0.4.9-116.el7.x86_64 device-mapper-multipath-devel-0.4.9-116.el7.x86_64 device-mapper-multipath-debuginfo-0.4.9-116.el7.x86_64 device-mapper-multipath-0.4.9-116.el7.x86_64 device-mapper-multipath-sysvinit-0.4.9-116.el7.x86_64 2, # multipathd show config device { vendor "Nimble" product "Server" path_grouping_policy "group_by_prio" path_selector "round-robin 0" path_checker "tur" <----------------------------------- features "1 queue_if_no_path" hardware_handler "1 alua" prio "alua" failback immediate dev_loss_tmo "infinity" } Test result: added TUR path checker to default hardware table for Nimble devices
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, 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/RHEA-2018:0884