DeleteFile doesn't return an error even when the server replies with "STATUS_NETWORK_NAME_DELETED" error

This problem may occur if the server encounters an error while it's processing the client DeleteFile request. For example, this may occur when there's a problem accessing the file system, or if the network connection between the client and server is lost. In order to trigger this problem, this error must occur within a very brief timing window, during the DeleteFile request.

This problem was discovered during stress testing of transparent failover, where the file system is brought down and back up while file operations are in progress. After the error, the server may continue to persist the open file handle and wait for a persistent reconnect to occur. Because the client application was not notified of an error, no persistent reconnect occurs. Therefore, the file remains until the server eventually deletes it when the persistent reconnect time-out period expires. (This last behavior occurs because the file handle is in a "delete-on-close" state on the server.)