Bug 1397090 - [NetApp 7.2 Bug]: Tur path_checker reports path status as UP in message file when paths are in failed state
Summary: [NetApp 7.2 Bug]: Tur path_checker reports path status as UP in message file ...
Keywords:
Status: CLOSED DUPLICATE of bug 1280524
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 15:18 UTC by Abhishek Kumar
Modified: 2021-09-03 12:04 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 23:39:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Abhishek Kumar 2016-11-21 15:18:13 UTC
Description of problem:

With GA kernel of RHEL7.2 we have observed that tur path_checker reporting path as UP in messages file even when the path is in failed faulty state.

from below messages file we observe that tur path_checker reporting paths as up but multipath output clearly shows that those paths are in failed faulty state.
 
from /var/log/messages:

Feb 29 16:56:06 ibmx3650m4-210-145 multipathd: 3600a09803830344674244644694e6e76: sdac - tur checker reports path is up 

Feb 29 16:56:06 ibmx3650m4-210-145 multipathd: 3600a09803830344674244644694e6e79: sdaf - tur checker reports path is up 

Feb 29 16:56:06 ibmx3650m4-210-145 multipathd: 3600a0980383034444824464c59386466: sdap - tur checker reports path is up 

Feb 29 16:56:06 ibmx3650m4-210-145 multipathd: 3600a0980383034444824464c59386467: sdaq - tur checker reports path is up

[root@ibmx3650m4-210-145 ~]# multipath -ll | grep sdac
   |- 0:0:7:20  sdac  65:192  failed faulty running
[root@ibmx3650m4-210-145 ~]#
[root@ibmx3650m4-210-145 ~]# multipath -ll | grep sdaf
   |- 0:0:7:23  sdaf  65:240  failed faulty running
[root@ibmx3650m4-210-145 ~]# multipath -ll | grep sdap
   |- 0:0:7:33  sdap  66:144  failed faulty running
[root@ibmx3650m4-210-145 ~]# multipath -ll | grep sdaq
   |- 0:0:7:34  sdaq  66:160  failed faulty running

Feb 29 16:54:26 ibmx3650m4-210-144 multipathd: 3600a0980383034444824464c59386461: sdan - tur checker reports path is up 

Feb 29 16:54:26 ibmx3650m4-210-144 multipathd: 3600a0980383034444824464c59386462: sdao - tur checker reports path is up 

Feb 29 16:54:26 ibmx3650m4-210-144 multipathd: 3600a09803830345877244644686c4e4d: sdf - tur checker reports path is up 

Feb 29 16:54:26 ibmx3650m4-210-144 multipathd: 3600a09803830344674244644694e6f6c: sdap - tur checker reports path is up 

Feb 29 16:54:26 ibmx3650m4-210-144 multipathd:  3600a09803830345877244644686c4f4f: sdas - tur checker reports path is up


[root@ibmx3650m4-210-144 ~]# multipath -ll | grep -i sdan
   |- 1:0:1:38  sdan  66:112  failed faulty running
[root@ibmx3650m4-210-144 ~]# multipath -ll | grep -i sdao
   |- 1:0:1:39  sdao  66:128  failed faulty running
[root@ibmx3650m4-210-144 ~]# multipath -ll | grep -i sdf
| |- 1:0:1:4   sdf   8:80    failed faulty running
[root@ibmx3650m4-210-144 ~]# multipath -ll | grep -i sdap
   |- 1:0:1:40  sdap  66:144  failed faulty running
[root@ibmx3650m4-210-144 ~]# multipath -ll | grep -i sdas
| `- 1:0:1:43  sdas  66:192  failed faulty running




Version-Release number of selected component (if applicable):

OS - RHEL 7.2 
How reproducible:


Steps to Reproduce:
1. Install RHEL7U2 on a SAN LUN
2. Map 40 LUN and configure DMMP and LV on all LUNs 
3. Create EXT4 and XFS file systems on LVs, and mount them 
4. Start IO to all mount points 
5. Start storage faults on the controllers 
6. while Storage node goes down eventually paths coming from that node also goes down but still tur path_checker reports path as UP


Actual results:

Tur path_checker reports path as up for failed faulty path


Expected results:

Tur path_checker should report path as down for failed faulty path
Additional info:

Comment 1 Ben Marzinski 2016-11-21 15:48:19 UTC
Can you please see if this is reproducible with the RHEL-7.3 device-mapper-multipath code.  I believe that this issue has been fixed in device-mapper-multipath-0.4.9-87.el7 and later by the changes for Bug 1280524.

Comment 2 Abhishek Kumar 2016-11-22 11:50:22 UTC
i dint see this issue with RHEL7.3 GA.

we don't have access to Bug 1280524.can you please provide the access?

Comment 4 Ben Marzinski 2016-11-29 23:30:39 UTC
You should have access to Bug 1280524 now.

Comment 5 Ben Marzinski 2016-11-29 23:39:55 UTC

*** This bug has been marked as a duplicate of bug 1280524 ***


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