Re: [Users] iSCSI discovery not showing all LUNs - oVirt 3.1
On 07/05/2012 06:08 PM, Trey Dockendorf wrote:
I have a Promise M300i iSCSI with 2 LUNs. A 2TB LUN with ID
2260-0001-557c-af0a and a 4TB LUN with ID 22d9-0001-553e-4d6a.
What's strange, is the very first time I ran discovery I saw both
LUNs. I checked the 2TB LUN and storage failed to add, I don't have
logs at this time, but I went back to repeat the process and now only
1 LUN shows in the GUI (see attached image). Also the size it reports
is way off.
Looking at VDSM logs, I get this output when doing the login to a target
{'devList':
[
{'vendorID': 'Promise',
'capacity': '2188028149760',
'fwrev': '0227',
'partitioned': False,
'vgUUID': 'AZ1iMt-gzBD-2uug-xTih-1z0b-PqPy-xSP0A4',
'pathlist': [
{
'initiatorname': 'default',
'connection': '192.168.203.100',
'iqn': 'iqn.1994-12.com.promise.xxx',
'portal': '1',
'password': '******',
'port': '3260'
}
],
'logicalblocksize': '512',
'pathstatus': [
{
'physdev': 'sde',
'type': 'iSCSI',
'state': 'active',
'lun': '0'
}
],
'devtype': 'iSCSI',
'physicalblocksize': '512',
'pvUUID': 'v2N3ok-wrki-OQQn-1XFL-w69n-8wAF-rmCFWt',
'serial':
'SPromise_VTrak_M300i_000000000000000000000000F08989F89FFF6C42',
'GUID': '222600001557caf0a',
'productID': 'VTrak M300i'
},
{
'vendorID': 'Promise',
'capacity': '20246190096384',
'fwrev': '0227',
'partitioned': False,
'vgUUID': '',
'pathlist': [
{
'initiatorname': 'default',
'connection': '192.168.203.100',
'iqn': 'iqn.1994-12.com.promise.xxx',
'portal': '1',
'password': '******',
'port': '3260'
}
],
'logicalblocksize': '2048',
'pathstatus': [
{
'physdev': 'sdf',
'type': 'iSCSI',
'state': 'active',
'lun': '1'
}
],
'devtype': 'iSCSI',
'physicalblocksize': '2048',
'pvUUID': '',
'serial':
'SPromise_VTrak_M300i_000000000000000000000000DA3FF8D8099662D7',
'GUID': '222d90001553e4d6a',
'productID': 'VTrak M300i'
}
]
}
In that output both LUNs are seen. I couldn't tell from the code what
format the "capacity" is in, but now the interface shows only the LUN
with the "4d6a" GUID as being 18TB.
I've attached the VDSM Logs from the point of selecting my datacenter
to after clicking "Login". Any suggestions?
node - vdsm-4.10.0-2.el6.x86_64
Thanks
- Trey
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
the LUN you don't see is 'dirty' and vdsm filters it.
there are some patches for showing all LUNs and just graying them out at
ui level (but these are post ovirt 3.1.
dd with zeros the start of your LUN should bring it back