Bug 1043811 - the dm and path status is 'failed faulty offline' on initial when run 'multipath -ll' after fcoe-target service restart on target
Summary: the dm and path status is 'failed faulty offline' on initial when run 'multip...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fcoe-target-utils
Version: 6.5
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: 6.6
Assignee: Maurizio Lombardi
QA Contact: Storage QE
URL:
Whiteboard:
Depends On: 970471
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 09:33 UTC by yanfu,wang
Modified: 2017-12-06 13:03 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 13:03:50 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description yanfu,wang 2013-12-17 09:33:27 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 yanfu,wang 2013-12-17 09:41:57 UTC
sorry type too fast, below is the Description of problem:
target is RHEL6.5 using fcoe-target-utils-2.0rc1.fb16-5.el6.noarch
initial is RHEL7 using device-mapper-multipath-0.4.9-58.el7.x86_64
The issue found during testing bug 882060.
target: st51 ixgbe FCoE target
/tcm_fc> ls
o- tcm_fc .............................................................................................................. [2 Targets]
  o- 20:00:00:1b:21:3f:a1:b6 ............................................................................................. [enabled]
  | o- acls ................................................................................................................ [1 ACL]
  | | o- 10:00:00:05:33:26:9e:4e ................................................................................... [3 Mapped LUNs]
  | |   o- mapped_lun0 .................................................................................... [lun0 fileio/disk1 (rw)]
  | |   o- mapped_lun1 .................................................................................... [lun1 fileio/disk3 (rw)]
  | |   o- mapped_lun2 .................................................................................... [lun2 fileio/disk2 (rw)]
  | o- luns ............................................................................................................... [3 LUNs]
  |   o- lun0 ...................................................................................... [fileio/disk1 (/tmp/fcoe-lun1)]
  |   o- lun1 ...................................................................................... [fileio/disk3 (/tmp/fcoe-lun3)]
  |   o- lun2 ...................................................................................... [fileio/disk2 (/tmp/fcoe-lun2)]
  o- 20:00:00:1b:21:3f:a1:b7 ............................................................................................. [enabled]
    o- acls ................................................................................................................ [1 ACL]
    | o- 10:00:00:05:33:26:9e:4e ................................................................................... [3 Mapped LUNs]
    |   o- mapped_lun0 .................................................................................... [lun0 fileio/disk2 (rw)]
    |   o- mapped_lun1 .................................................................................... [lun1 fileio/disk1 (rw)]
    |   o- mapped_lun2 .................................................................................... [lun2 fileio/disk3 (rw)]
    o- luns ............................................................................................................... [3 LUNs]
      o- lun0 ...................................................................................... [fileio/disk2 (/tmp/fcoe-lun2)]
      o- lun1 ...................................................................................... [fileio/disk1 (/tmp/fcoe-lun1)]
      o- lun2 ...................................................................................... [fileio/disk3 (/tmp/fcoe-lun3)]

initial is st52: bfa FCoE CNA

Restart fcoe-target on target:
[root@storageqe-51 ~]# service fcoe-target restart

Then run multipath -ll on initial:
[root@storageqe-52 host0]# echo 1 > issue_lip
[root@storageqe-52 host0]# multipath -ll
...
mpathi (36001405d3b266414b05408bac1e2cfee) dm-13 LIO-ORG ,FILEIO          
size=10G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| `- 0:0:7:2 sdaa 65:160 failed faulty offline
`-+- policy='service-time 0' prio=0 status=enabled
  `- 0:0:6:1 sdx  65:112 failed faulty offline
mpathh (3600140500bf5110e49e41d48ef38f1e5) dm-12 LIO-ORG ,FILEIO          
size=10G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| `- 0:0:6:2 sdy  65:128 failed faulty offline
`-+- policy='service-time 0' prio=0 status=enabled
  `- 0:0:7:0 sdw  65:96  failed faulty offline
mpathg (36001405bb719b6cbb5f4cdc8ba39b25d) dm-11 LIO-ORG ,FILEIO          
size=10G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| `- 0:0:7:1 sdz  65:144 failed faulty offline
`-+- policy='service-time 0' prio=0 status=enabled
  `- 0:0:6:0 sdv  65:80  failed faulty offline
                         ^^^^^^^^^^^^^^^^^^^^^

wait several minutes and multipath shown, but with 'failed faulty offline' status.

The kernel part bug is 970471.

Comment 3 Jan Kurik 2017-12-06 13:03:50 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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