The NFS server uses UMNT as a signal to remove the client from its mount table. Also at this time the Server cleans up other information about the now disconnected client. Why would the client attempt to access the NFS server once it has stated its going to unmount? I do not see the point of the GETATTR request after UMNT call. Christopher Vogan Dept. W98 NFS Development & Test From: "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> To: Christopher T Vogan/San Jose/IBM@IBMUS, Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx> Date: 06/18/2013 10:19 AM Subject: Re: NFSERR_STALE on umount with 3.10.0.RC5 kernel On Tue, 2013-06-18 at 07:47 -0600, Christopher T Vogan wrote: > The new linux 3.10.0-rc5 kernel gets NFSERR_STALE on un-mount. > The reason is the Linux client is sending a GETATTR after the umnt > call/reply. > This is a network trace of the umnt call/reply and the gettattr > afterwords. This happens because the 'umount.nfs' utility calls the umnt RPC before the actual umount system call. Why would this trigger an NFSERR_STALE? Is the server using UMNT for something other than just providing client usage stats? If so, what and why? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.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
