On Nov 11, 2013, at 11:50, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > Hi- > > It was recently pointed out to me that the behavior of atime on NFS mount points is pretty dodgy, yet this is not documented anywhere, not even in the venerable and unmaintained Linux NFS FAQ. > > A good place to cover this topic might be nfs(5). It could discuss how the Linux NFS client deals with the various *atime mount options (mostly be collapsing them into relatime, all the time). And it could discuss how file timestamps are updated when the physical backing store is on another system. > > Thoughts? Comments? NFS atime is not the same as relatime. Our atime is only updated when a READ rpc call goes to the server. Cached reads do not, for instance, trigger an atime update. That is a very different model than the relatime model. Cheers Trond-- 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
