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

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 218218
           Summary: bad atime after cp on linux nfs4 clients
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jim at ks.uiuc.edu

Just updated from 10.2 to 11.0-RELEASE-p8, also happens on 10.2 and 10.3.
Accessing ZFS filesystem via nfs4 from CentOS 6.5 and 7.3 clients.

When using cp the resulting file has an access time in the far future.
On CentOs 6.5 client accessing the file produces a reasonable access time, but
not on CentOS 7.3.  Centos 5.6 does not have the issue at all.

jim at sunnyvale$echo "test" > foo
jim at sunnyvale$ls -l --time=atime
total 7
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo
jim at sunnyvale$/bin/cp foo foo2
jim at sunnyvale$ls -l --time=atime
total 13
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo
-rw-r--r-- 1 jim etguest 5 Jan  4  2091 foo2
jim at sunnyvale$cat foo2 > /dev/null
jim at sunnyvale$ls -l --time=atime
total 13
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo2
jim at sunnyvale$/bin/cp foo foo3
jim at sunnyvale$ls -l --time=atime
total 14
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo
-rw-r--r-- 1 jim etguest 5 Mar 29 15:23 foo2
-rw-r--r-- 1 jim etguest 5 Jan  5  2091 foo3

Note that on the server the time is in the far past rather than the far future:

root at adrastea:/foo/test # ls -l -u
total 20
-rw-r--r--  1 14522  1014  5 Mar 29 15:23 foo
-rw-r--r--  1 14522  1014  5 Mar 29 15:23 foo2
-rw-r--r--  1 14522  1014  5 Nov 30  1954 foo3

Options shown in /proc/mounts on the CentOS 6.5 client are
nfs4
rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=130.126.120.168,minorversion=0,local_lock=none,addr=130.126.120.98
0 0

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