Sorry for a slow reply - this is unfortunately not the only bug I am working on. After further testing, this problem does actually reproduce with synchronous mounts as well as asynchronous mounts. It just takes some extreme stress testing to reproduce with synchronous mounts. After some debugging in xs_tcp_shutdown() (a cheeky dump_stack()), it appears that periodically xprt_autoclose() is closing the TCP connection. It appears that some of the time, the server correctly FIN+ACKs the first FIN, at which point the TCP connection is torn down and set back up, with no interruption to the NFS session. However, some of the time, the server does not FIN+ACK the clients FIN, at which point the client waits 15 seconds and RST's the TCP connection, leading to the errors seen. What is the purpose of xprt_autoclose() ? I assume it is to automatically close idle connections. Am I correct in assuming that it should not be attempting to close an active connection? Thanks, -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
