Hi,
I noticed that when I add two LIO based iSCSI storages to a Linux box
running Veritas volume manager that it will think all LIO targets are
"the same" enclosure.
An enclosure is detected by the multipath drivers in VxVM. I think they
use some sort of scsi serial number or something to identify that.
(I know there's API drivers that are "certified" but thats for extra
features)
So, anyway.
I would have thought the "array" presented by system "Sechs" should end
up with a different name than the "array" presented by my laptop.
Rationale & Steps:
------------------
I needed to provide storage for a lab and used LIO on Fedora 16 for that.
I basically made one "storage box" serving via iSCSI, with just 6 1GB luns.
On the client (Centos6.2) I've installed Veritas SF basic and everything
worked OK.
I can see an "enclosure" for my LIO target and have made it name the
disks by the presented LUN numbers:
[root@Zwei plugins]# vxdmpadm listenclosure
ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE
LUN_COUNT
=======================================================================================
other_disks OTHER_DISKS OTHER_DISKS CONNECTED
OTHER_DISKS 1
LIO-Sechs aluadisk ALUAdisk CONNECTED ALUA
9
[root@Zwei plugins]# vxdisk list
DEVICE TYPE DISK GROUP STATUS
LIO-Sechs_0 auto:cdsdisk LIO-Sechs_0 datadg online
LIO-Sechs_1 auto:cdsdisk LIO-Sechs_1 datadg online
LIO-Sechs_2 auto:cdsdisk LIO-Sechs_2 datadg online
LIO-Sechs_3 auto:none - - online invalid
LIO-Sechs_4 auto:none - - online invalid
LIO-Sechs_5 auto:none - - online invalid
sda auto:none - - online invalid
Now after scanning I get 3 new disks (6-8), but they're named after the
enclosure "LIO-Sechs"
[root@Zwei plugins]# vxdisk scandisks
[root@Zwei plugins]# vxdisk list
DEVICE TYPE DISK GROUP STATUS
LIO-Sechs_0 auto:cdsdisk LIO-Sechs_0 datadg online
LIO-Sechs_1 auto:cdsdisk LIO-Sechs_1 datadg online
LIO-Sechs_2 auto:cdsdisk LIO-Sechs_2 datadg online
LIO-Sechs_3 auto:none - - online invalid
LIO-Sechs_4 auto:none - - online invalid
LIO-Sechs_5 auto:none - - online invalid
LIO-Sechs_6 auto - - error
LIO-Sechs_7 auto - - error
LIO-Sechs_8 auto - - error
sda auto:none - - online invalid
This is because the volume manager (or more exactly, it's alua driver)
came to think all these LUNs come from the same array.
[root@Zwei plugins]# vxdmpadm listenclosure
ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE
LUN_COUNT
=======================================================================================
other_disks OTHER_DISKS OTHER_DISKS CONNECTED
OTHER_DISKS 1
LIO-Sechs aluadisk ALUAdisk CONNECTED ALUA
9
This means that a lot things can go wrong, i.e. mirrors being mis-located.
My question is now if anyone else can verify this or if they know where
LIO sets calculates it's scsi serial numbers and device description.
I have already checked the serial numbers. he is for 2 consecutive luns
from the first LIO box and 2 from the second.
udid: LIO-ORG%5FFILEIO%5FALUAdisk%5F600140524EBE4E5D6F448398558D778E
udid: LIO-ORG%5FFILEIO%5FALUAdisk%5F6001405A4729837F3D54BD6B467D5215
udid: LIO-ORG%5FFILEIO%5FALUAdisk%5F600140570C836BD57C94B99BB201790F
udid: LIO-ORG%5FFILEIO%5FALUAdisk%5F60014058123A0B0A8824DEC8469BEBAC
It doesn't seem like a node id or such is encoded there.
Any pointers on how to mess with these serials?
Are there any plans for getting Veritas certification like the VMWare
one? It might still down the road until companies replace their Vmax
with LIO, but it can't hurt to pave the way :)
(Especially since thin provisioning / reclamation is done with those
libraries)
Greetings,
Florian
--
Mathias Kettner GmbH
Registergericht: Amtsgericht München, HRB 165902
Firmensitz: Preysingstraße 74, 81667 München
Geschäftsführer: Mathias Kettner
Tel. 089 / 1890 4210
Fax 089 / 1890 4211
http://mathias-kettner.de
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
