On Fri, Oct 31, 2014 at 01:31:36PM +0200, Trond Myklebust wrote: > If there is no read on the wire, then there is no way to update the > atime without doing an explicit SETATTR. Courtesy of POSIX filesystem > semantics on the server, that means we get a bonus change attribute > and ctime update (no extra charge). > > Unless there are new suggestions for how to solve the atime issue that > do not involve introducing this or similar regressions, then the > standing NACK applies. I think various network filesystems are fairly lax on updating the atime on the server. What xfstests generic/192 tests is that we don't lose an atime update after an unmount/remount. I think we should be able to expect local atime updates, and updates to the server on unmount. Or at least claim that the filesystem is mounted by noatime if it is so that users (including xfstests) notice, and can enable strict atime mode if really needed, including the above mentioned drawbacks. -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
