On Wed Nov 18, 2026 at 6:14 PM CET, Chuck Lever wrote: > > > On Wed, Nov 18, 2026, at 11:36 AM, Amir Goldstein wrote: >> Can't an NFS client be connected to another NFS server >> implementation which does allow this? >> >> I can't wrap my head around the problem. > > You already named the problem in a previous email: What happens > when the NFS server's kernel is upgraded from an NFSD that exposes > only btime to one that picks either ptime or btime? > > Clients will see a file's btime before the server restart, and > afterwards, they will see a changed TIME_CREATE but the file's > NFSv4 change attribute will be unchanged. Not really though, newly created files will have btime == ptime, and for older files ptime won't be set until someone sets it. If the underlying filesystem changes it, then it's the same situation as if someone on the server manually changed a/c/mtime on the underlying filesystem without informing the NFS server. Although, I'm not sure if my current code in this patch updates iversion on ptime change, if that's the case I'll fix it for v5 since it'd be a bug. Thanks, koraynilay