I have a machine that is attached to an iSCSI target stored in a 50GB zvol in a zfs pool. I am copying roughly 25GB of data from that target to another drive and seeing some failures, as well as several errors in the Event Log.
First, in the Windows Event Log, I see a bunch of the following when the problem happens: Event Type: Error Event Source: iScsiPrt Event Category: None Event ID: 42 Date: 1/16/2008 Time: 12:14:24 AM User: N/A Computer: NTORAEXP1 Description: Target sent an invalid status sequence number for a connection. Dump data contains Expected Status Sequence number followed by the given status sequence number. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 08 00 01 00 62 00 ......b. 0008: 00 00 00 00 2a 00 00 c0 ....*..À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 82 02 00 00 83 02 00 00 ...... Second, while watching the target statistics on the Solaris box, I see the following: #iscsitadm show stats -I 5 pool/iscsi/osa2 operations bandwidth device read write read write -------------------- ----- ----- ----- ----- pool/iscsi/osa2 0 6 0K 24K pool/iscsi/osa2 1K 2 100M 8K pool/iscsi/osa2 1K 0 126M 0K pool/iscsi/osa2 1K 0 120M 0K pool/iscsi/osa2 1K 0 98M 0K pool/iscsi/osa2 1K 0 119M 0K pool/iscsi/osa2 1014 0 63M 0K pool/iscsi/osa2 0 3 0K 12K pool/iscsi/osa2 1K 6 79M 24K pool/iscsi/osa2 1K 2 62M 8K pool/iscsi/osa2 456 2 21M 8K pool/iscsi/osa2 1K 0 122M 0K pool/iscsi/osa2 1K 0 109M 0K pool/iscsi/osa2 1K 3 119M 12K pool/iscsi/osa2 478 3 30M 12K pool/iscsi/osa2 0 4 0K 16K pool/iscsi/osa2 0 2 0K 8K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 1 0K 4K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 0 0 0K 0K pool/iscsi/osa2 4.0G 4.0G 2.0T 2.0T <==== ???? pool/iscsi/osa2 2 0 1K 0K ... I have to disable/enable the iSCSI target on the Solaris box to be able to use the device again. Even rebooting the iSCSI client doesn't allow me back into the volume again. Any thoughts on what I can do to solve this? This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
