Yes..Hmm, these traces are not showing anything obviously wrong.
For 'iscsi-login-crash-2', I'm seeing:
Packet#17, Initiator->Target, TCP Len: 520,
iSCSI (Login Command)
Opcode: Login Command (0x03)
1... .... = T: Transit to next login stage
.0.. .... = C: Text is complete
.... 01.. = CSG: Operational negotiation (0x01)
.... ..11 = NSG: Full feature phase (0x03)
VersionMax: 0x00
VersionMin: 0x00
TotalAHSLength: 0x00
DataSegmentLength: 0x000001d8
ISID: 00023D000000
00.. .... = ISID_t: IEEE OUI (0x00)
..00 0000 = ISID_a: 0x00
ISID_b: 0x023d
ISID_c: 0x00
ISID_d: 0x0000
TSIH: 0x0000
InitiatorTaskTag: 0x000a0000
CID: 0x0000
CmdSN: 0x00000000
ExpStatSN: 0x00000000
Key/Value Pairs
KeyValue: InitiatorName=iqn.1996-04.de.suse:01.f55caa69a4db
KeyValue: InitiatorAlias=thing1
KeyValue:
TargetName=iqn.1986-03.com.sun:02:b0f5eaa2-28d5-4960-9210-b212a505a9f1
KeyValue: SessionType=Normal
KeyValue: HeaderDigest=None
KeyValue: DataDigest=None
KeyValue: DefaultTime2Wait=0
KeyValue: DefaultTime2Retain=0
KeyValue: IFMarker=No
KeyValue: OFMarker=No
KeyValue: ErrorRecoveryLevel=0
KeyValue: InitialR2T=No
KeyValue: ImmediateData=Yes
KeyValue: MaxBurstLength=16776192
KeyValue: FirstBurstLength=262144
KeyValue: MaxOutstandingR2T=1
KeyValue: MaxConnections=1
KeyValue: DataPDUInOrder=Yes
KeyValue: DataSequenceInOrder=Yes
KeyValue: MaxRecvDataSegmentLength=65536
Packet#19, Target->Initiator, TCP Len: 48,
iSCSI (Login Response)
Opcode: Login Response (0x23)
1... .... = T: Transit to next login stage
.0.. .... = C: Text is complete
.... 01.. = CSG: Operational negotiation (0x01)
.... ..11 = NSG: Full feature phase (0x03)
VersionMax: 0x02
VersionActive: 0x00
TotalAHSLength: 0x00
DataSegmentLength: 0x00000169
ISID: 00023D000000
00.. .... = ISID_t: IEEE OUI (0x00)
..00 0000 = ISID_a: 0x00
ISID_b: 0x023d
ISID_c: 0x00
ISID_d: 0x0000
TSIH: 0x0005
InitiatorTaskTag: 0x000a0000
StatSN: 0x00000000
ExpCmdSN: 0x00000000
MaxCmdSN: 0x00000001
Status: Success (0x0000)
Packet#20, Target->Initiator, (Continuation to #19), TCP Len: 361,
TargetAlias=xen/crossroads
TargetPortalGroupTag=1
HeaderDigest=None
DataDigest=None
DefaultTime2Wait=0
DefaultTime2Retain=0
IFMarker=No
OFMarker=No
ErrorRecoveryLevel=0
InitialR2T=Yes
ImmediateData=Yes
MaxBurstLength=16776192
FirstBurstLength=262144
MaxOutstandingR2T=1
MaxConnections=1
DataPDUInOrder=Yes
DataSequenceInOrder=Yes
MaxRecvDataSegmentLength=65536
Packet#21, Target->Initiator, (Continuation to #19), TCP Len: 3,
(Data is just zero three zero bytes "00 00 00")
The Initiator then ACK those packets, then nothing more...Right?
I'm not sure what packet#21 is trying to convey - maybe that's the problem,
but I'm just guessing.
Is any one else seeing any sort of problem here?
Could you enable some debugging/error logs from the Linux side?
And could you use strace to see what the Initiator process is doing?
Thanks
Nigel Smith
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[EMAIL PROTECTED]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
