[storage-discuss] Re: Re: Packages available with fix for Microsoft
Nigel Smith
nwsmith at wilusa.freeserve.co.uk
Tue Jan 30 15:18:13 PST 2007
Could it be that the Target's "NOP In (0x20)" are incrementing StatSN, when the Microsoft Initiator, thinks it should not be doing so?
In the trace I'm currently looking at, I see the solaris target sending the following sequence of (4) packets:
#1 - "SCSI Data In", StatSN = 0x2a
#2 - "NOP In", StatSN = 0x2b
#3 - "NOP In", StatSN = 0x2c
#4 - "SCSI Data In", StatSN = 0x2d
...At which point the Microsoft Initiator says:
Invalid status seq num 0x2d. Current is 0x2b
Thanks
Nigel
This message posted from opensolaris.org
More information about the storage-discuss
mailing list