This last update on the problem was new information gathered after our last exchange on 6/18/2013. We also suspected the issue to be related to "cto", but adding mount options "nocto" did not resolve the problem. Christopher Vogan Dept. W98 NFS Development & Test From: "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> To: Christopher T Vogan/San Jose/IBM@IBMUS, Jeff Layton <jlayton@xxxxxxxxxx>, Cc: "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx>, Steve Dickson <SteveD@xxxxxxxxxx> Date: 06/26/2013 07:51 PM Subject: Re: NFSERR_STALE on umount with 3.10.0.RC5 kernel On Wed, 2013-06-26 at 15:24 -0600, Christopher T Vogan wrote: > This is a complete network trace between the client and server. > > > So this issue only happens on Kernels 3.9.6 and newer. > I did not have this problem with Kernel 3.8.13 > nfs-utils-1.2.3-36 (from Redhat) was used w/ all kernel versions. Ah. I don't recall seeing that information before. In that case, I'm guessing that the change in behaviour is likely to be commit ecf3d1f1aa74da0d632b651a2e05a911f60e92c0 (vfs: kill FS_REVAL_DOT by adding a d_weak_revalidate dentry op). Jeff, any comment on what behaviour you expect on umount() post-ecf3d1f1aa? -- 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
