[Bug 270842] nfsclient sees out-of-date metadata until stat(1)

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 15 Apr 2023 21:58:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270842

--- Comment #8 from Rick Macklem <rmacklem@FreeBSD.org> ---
(In reply to Alan Somers from comment #7)
Yes, but whether or not there is a name cache miss
is a big question. Part of that is the test that
the NFS client does for ctime changing for the
directory the name is in.

Short version. The semantics of this has not changed
in well over a decade. The only difference introduced
by NFSv4 (for the non-delegation case) is a new attribute
called Change that should be guaranteed to change whenever
a file's data or metadata changes. (NFSv3 used mtime and
ctime, which depended upon file system time resolution
and to a lesser extent, when the file system updated
ctime, which was not very well specified in POSIX.)

Recall that NFS is not (and cannot be) a POSIX compliant
file system, due to its protocol design.

Set acregmax and acregmin to 0 and see what happens?
(Just be prepared for a performance hit and much higher
Getattr RPC counts on the NFS server.)

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