Microsoft KB972886 iSCSI Software Target, v.KB972886, A00

2484 iSCSI Target in a Cluster is clearing all Assigned LUNMappings right after AddWTDisk.
Scenario: App calls WMI method AddWTDisk on a clustered iSCSI target, then the resource group fails over to another cluster node
Effect: After the failover the iSCSI target loses all its LUN mappings. The LUNs are surprise removed from the initiators (which can also cause some data loss). Admin has to recreate the mappings.

2796 Target AVs when initiator formats LUN
Scenario: Initiator formats a LUN on iSCSI target with Mutual Chap and Header and Data Digest turned on
Effect: iSCSI target service crashes

3018 WinTarget fails to release login lock if the login process fails or aborts prematurely in a cluster
Scenario: The title is self-explanatory.
Effect: Deadlock of the iSCSI target service. The iSCSI resources go offline.

3195 Snapshotmgr/snapshot lock not taken in same order, causing deadlock
Scenario: VSS call to create exportable snapshot of a vhd collides with deletion of a vhd
Effect: Deadlock of the iSCSI target service

3319 Scalability: Large scale cluster did not failover until forced shutdown and restart
Scenario: There are many potential scenarios for this bug. They all have something to do with race conditions between the IsAlive call that the cluster makes every 5 seconds into the iSCSI target service to check the status of the resources and various administration/login operations. This is more likely to hit on systems with large number of targets/vhds.
Effect: Deadlock of the iSCSI target service and its cluster resource DLL. The iSCSI resources go offline. Cluster need to be shutdown and restarted.

3600 IO Stress: Cluster deadlock during I/O stress setup
Scenario: Race condition between multiple operations that require the iSCSI target service to call into the cluster service
Effect: Deadlock of the iSCSI target service.

3624 Cluster resource DLL leaks handles to the WinTarget service
Scenario: Configure a clustered iSCSI target and let it run for a while
Effect: A handle is leaked every 5 seconds. After a while the leaks add up and lead to system degradation.