Bug 650797

Summary: [NetApp 6.1 bug] "multipath -v3" displays tgt_node_name as blank for iscsi devices
Product: Red Hat Enterprise Linux 6 Reporter: Ben Marzinski <bmarzins>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Storage QE <storage-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: agk, bdonahue, bmarzins, christophe.varoqui, coughlan, cward, djansa, dwysocha, egoggin, fge, gowrav.mahadevaiah, heinzm, iannis, jbrassow, joe.thornber, junichi.nomura, kueda, lmb, mbroz, prajnoha, prockai, tanvi, tranlan, xdl-redhat-bugzilla
Target Milestone: rcKeywords: OtherQA
Target Release: 6.1   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, multipathd displayed no tgt_node_name value for iSCI devices. This occurred because multipath used the FC (Fibre Channel) path from the sysfs file system to obtain tgt_node_name for iSCI devices. With this update, multipath first tries to acquire the FC path. If it fails, it uses the iSCI target name for the device.
Story Points: ---
Clone Of: 512065 Environment:
Last Closed: 2011-05-19 14:12:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 512065    
Bug Blocks: 580566    

Comment 2 Ben Marzinski 2010-12-23 04:18:36 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
If multipath is unable to get a fc target name for a SCSI device, it will now try it get an ISCSI target name for the device.

Comment 5 Chris Ward 2011-04-06 11:15:59 UTC
~~ Partners and Customers ~~

This bug was included in RHEL 6.1 Beta. Please confirm the status of this request as soon as possible.

If you're having problems accessing 6.1 bits, are delayed in your test execution or find in testing that the request was not addressed adequately, please let us know.

Thanks!

Comment 6 gowrav 2011-04-07 06:11:48 UTC
I verified this bug on RHEL 6.1 OS, and the issue is fixed. Now, multipath -v3 cmd displays correct "tgt_node_name" names. Below is a snippet of command output.

Apr 07 11:36:49 | sdd: not found in pathvec
Apr 07 11:36:49 | sdd: mask = 0x1f
Apr 07 11:36:49 | sdd: dev_t = 8:48
Apr 07 11:36:49 | sdd: size = 65628160
Apr 07 11:36:49 | sdd: subsystem = scsi
Apr 07 11:36:49 | sdd: vendor = NETAPP
Apr 07 11:36:49 | sdd: product = LUN
Apr 07 11:36:49 | sdd: rev = 7350
Apr 07 11:36:49 | sdd: h:b:t:l = 61:0:0:0
Apr 07 11:36:49 | sdd: tgt_node_name = iqn.1992-08.com.netapp:sn.135026469
Apr 07 11:36:49 | sdd: serial = P3LMaJ/L1DgF
Apr 07 11:36:49 | sdd: get_state
Apr 07 11:36:49 | sdd: path checker = directio (controller setting)
Apr 07 11:36:49 | sdd: checker timeout = 30000 ms (sysfs setting)
Apr 07 11:36:49 | sdd: state = running

Kernel -- kernel-2.6.32-122.el6.x86_64
Multipath -- device-mapper-multipath-0.4.9-39.el6.x86_64

Comment 7 Eva Kopalova 2011-05-02 13:51:09 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-If multipath is unable to get a fc target name for a SCSI device, it will now try it get an ISCSI target name for the device.+Previously, multipathd displayed no tgt_node_name value for iSCI devices. This occurred because multipath used the FC (Fibre Channel) path from the sysfs file system to obtain tgt_node_name for iSCI devices. With this update, multipath first tries to acquire the FC path. If it fails, it uses the iSCI target name for the device.

Comment 8 errata-xmlrpc 2011-05-19 14:12:32 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0725.html