From owner-freebsd-fs@freebsd.org  Thu Mar 30 22:05:11 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69D89D2593D
 for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 30 Mar 2017 22:05:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 51399873
 for <freebsd-fs@FreeBSD.org>; Thu, 30 Mar 2017 22:05:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2UM5B6B005143
 for <freebsd-fs@FreeBSD.org>; Thu, 30 Mar 2017 22:05:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 218218] bad atime after cp on linux nfs4 clients
Date: Thu, 30 Mar 2017 22:05:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jim@ks.uiuc.edu
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 22:05:11 -0000

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

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

"relatime maintains atime data, but not for each time that a file is access=
ed.
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 j=
ust
seems to get stuck in the future after that.

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