[Bug 218218] bad atime after cp on linux nfs4 clients

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Mar 30 22:05:11 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218218

--- Comment #2 from Jim Phillips <jim at ks.uiuc.edu> ---
From
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Power_Management_Guide/Relatime.html

"relatime maintains atime data, but not for each time that a file is accessed.
With this option enabled, atime data is written to the disk only if the file
has been modified since the atime data was last updated (mtime), or if the file
was last accessed more than a certain amount of time ago (by default, one
day)."

By mounting with -o norelatime,strictatime I was able to make the relatime
option disappear from /proc/mounts, but the future atime issue is unchanged.

The issue is only the initial atime setting when the file is created.  It just
seems to get stuck in the future after that.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-fs mailing list