On Fri, 16 Aug 2013, Dave Chinner wrote:
The problem with "not exported, don't update" is that files can be modified on server startup (e.g. after a crash) or in short maintenance periods when the NFS service is down. When the server is started back up, the change number needs to indicate the file has been modified so that clients reconnecting to the server see the change. IOWs, even if the NFS server is not up or the filesystem not exported we still need to update change counts whenever a file changes if we are going to tell the NFS server that we keep them...
This sounds like you need something more like relctime rather than noctime, something that updates the time in ram, but doesn't insist on flushing it to disk immediatly, updating when convienient or when the file is closed.
David Lang -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
