kristof wrote: > Some time ago I experienced the same issue. > > Only 1 target could be connected from an esx host. Others were shown as > alternative paths to that target. > > If I'm reminding correctly I thought I read on a forum it has something to do > with the disks serial number.
Steffen Plotner summarised this well in http://communities.vmware.com/thread/60452 An optional VPD is exposed, and esx ignores the 'blank' serial/no, intended to tell the host that no s/n exists. >>VMware Communities > VMTN > Archives > >> VMware Infrastructure Archives > >> ESX Server 3.x Configuration Archives > Discussions >> Nov 1, 2006 >> Why does vmware think that 2 different LUNs are actually the same >> disk? Simple, they both have the same serial number. I have >> researched the problem and found that the SCSI specification >> exposes VPD (vital product data). One of those VPD is 0x83 which is >> the unit identification which IET implements and the specification >> requires it. The other page is 0x80 which is the disk serial number >> page, the specification says that this is optional, and IET sends >> back 4 0x20 codes which are spaces, the spec clearly says that's >> the way to tell the initiator that there is no serial number. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
