Hi. The theory is that the modified pages which need to get written to the server can't be released until they have been successfully written and committed to stable storage on the server. They can't disappear until they have been successfully transmitted and a response received. The problem here is that there were two requests sent or being sent and the page(s) can't be released until everyone, including TCP and such, are done with them. ps -----Original Message----- From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs-owner@xxxxxxxxxxxxxxx] On Behalf Of Alex Bligh Sent: Wednesday, January 23, 2013 12:42 PM To: Myklebust, Trond Cc: linux-nfs@xxxxxxxxxxxxxxx; ian.campbell@xxxxxxxxxx; Alex Bligh Subject: Re: Fatal crash with NFS, AIO & tcp retransmit Trond, --On 23 January 2013 17:37:08 +0000 "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> wrote: >> If you break the connection, and the written data is now not >> available to dom0 (as it's been mapped out), how would it ever get >> resent? IE it's not going to be available to the RPC layer either. > > There are typically more than 1 outstanding RPC call at any one time. > Breaking the connection would affect those other RPC calls. I understand that. I meant 'how does the write which failed ever get retransmitted now the data to be written has been lost?' -- Alex Bligh -- 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 -- 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
