KB958796

Consider the following scenario.

  • You use Microsoft iSCSI Initiator to connect to an iSCSI target from a computer that is running Windows Vista or Windows Server 2008.
  • A logical unit number (LUN) reset request is issued as part of a recovery action while a split transaction is being processed.

In this scenario, the iSCSI target does not respond. Within the next several minutes, more LUN reset requests are issued. However, the LUN reset never finishes. Eventually, the system drops the connection and then reconnects to the iSCSI target. Therefore, the whole recovery process may take much longer than expected to be completed. During this time, no I/O requests can be committed to the iSCSI target.

Additionally, event ID 63 may be logged in the System log.

Leave a Reply