Bug 1389524

Summary: "multipath -ll" command should show the LUN number linked to the mapper device
Product: Red Hat Ceph Storage Reporter: Hemanth Kumar <hyelloji>
Component: RBDAssignee: Mike Christie <mchristi>
Status: CLOSED WONTFIX QA Contact: Hemanth Kumar <hkumar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1CC: ceph-eng-bugs, jdillama, kdreyer
Target Milestone: rc   
Target Release: 2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 21:09:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Hemanth Kumar 2016-10-27 19:32:35 UTC 
Description of problem:
-------------------------
Output of "multipath -ll" doesn't give the proper details about the LUN's created.It should either display the Lun value or rbd image name configured for that particular LUN

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


# multipath -ll 

mpatha (36001405a05acdde9508402e98bef40d7) dm-0 LIO-ORG ,IBLOCK
size=800G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='queue-length 0' prio=0 status=enabled
| `- 7:0:0:0  sde  8:64   failed faulty running
|-+- policy='queue-length 0' prio=0 status=enabled
| `- 8:0:0:0  sdf  8:80   failed faulty running
|-+- policy='queue-length 0' prio=10 status=active
| `- 9:0:0:0  sdg  8:96   active ready  running
`-+- policy='queue-length 0' prio=10 status=enabled
  `- 10:0:0:0 sdh  8:112  active ready  running


It just displays the mapper device and dm-X as a name.
It's very difficult to find out the LUN which is mapped as device.
Comment 2 Mike Christie 2016-10-27 21:45:28 UTC 
This is definitely a bug.

I do not think it qualifies as a blocker, so 2.2 work. Adding devel ack for next release.
Comment 3 Jason Dillaman 2017-01-04 21:09:53 UTC 
This issue most likely only affects RHCS 2.1 since RHCS 2.2 will utilize a new approach for incorporating RBD-backed iSCSI.