Rasmus,
I had 4 volumes:-
Found 4 LU(s)
GUID DATA SIZE SOURCE
-------------------------------- ------------------- ----------------
600144f0b003090000004afb990f0004 1099511562240
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-03
600144f0b003090000004afb990e0003 1099511562240
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-02
600144f0b003090000004afb990d0002 2196875706368
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-01
600144f0b003090000004afb990c0001 2196875706368
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-00
I've reallocated these same LUN's to a Windows server (a VM with MS iSCSI
initiator) and this works fine.
One your posting below I've created a new 1024GB LUN and tried allocated this
and only this LUN to vSphere, but I'm getting the same issue. Here are the new
details:-
GUID DATA SIZE SOURCE
-------------------------------- ------------------- ----------------
600144f0b003090000004afbac8a0007 1099511562240
/dev/zvol/rdsk/infobrick/iscsi/prmel1vspcor-jhgtier2-04
# stmfadm list-view -l 600144f0b003090000004afbac8a0007
View Entry: 0
Host group : prmel1vspcor
Target group : All
LUN : 0
# stmfadm list-hg -v
Host Group: prmel1vspcor
Member: iqn.1998-01.com.vmware:prmel1vspcor02-74207c44
Unfortunately there is no change to the behaviour - same errors in the
/var/log/vmkernel:-
Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan:
839: Path 'vmhba34:C0:T0:L0': Vendor: 'SUN ' Model: 'COMSTAR '
Rev: '1.0 '
Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan:
842: Path 'vmhba34:C0:T0:L0': Type: 0x1f, ANSI rev: 5, TPGS: 0 (none)
Nov 12 17:29:35 PRMEL1VSPCOR02 vmkernel: 0:01:15:02.440 cpu6:4252)ScsiScan:
105: Path 'vmhba34:C0:T0:L0': Peripheral qualifier 0x1 not supported
...
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba34:CH:2 T:0 CN:0: Failed to receive
data: Connection closed by peer
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 172.22.205.39:52606 R:
172.22.205.27:3260]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: vmhba34:CH:2 T:0 CN:0: Connection rx notifying
failure: Failed to Receive. State=Online
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)iscsi_vmk:
iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 172.22.205.39:52606 R:
172.22.205.27:3260]
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: vmhba34:CH:2 T:0 CN:0: Processing CLEANUP
event
Nov 12 17:35:05 PRMEL1VSPCOR02 vmkernel: 0:00:02:30.505 cpu1:4241)WARNING:
iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000003 TARGET:
iqn.1986-03.com.sun:02:dd37a032-4edf-cdb5-a1aa-81726262d094 TPGT: 2 TSIH: 0]
...
I've even tried a reboot of my vSphere server just to be sure that nothing was
invalid there (btw, CHAP is currently disabled as well), but no good.
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
