Date: Thu, 30 Mar 2017 22:05:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218218] bad atime after cp on linux nfs4 clients Message-ID: <bug-218218-3630-Qx3d0CTNIQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218218-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-218218-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218218 --- Comment #2 from Jim Phillips <jim@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218218-3630-Qx3d0CTNIQ>