NFS Close-to-Open Consistency
An NFS cache-consistency approach in which updates are pushed on close and another client revalidates file state when opening the file.
NFS clients cache file data and attributes for performance, so a completed write on one client cannot simply be assumed to become visible to every other client with local-filesystem timing. Close-to-open consistency creates a practical visibility boundary by pushing changes at close and revalidating cached state when another client opens the file.
This is not a distributed transaction guarantee. Attribute-cache timing, mount options, protocol version and whether an application keeps a file open can all affect observed behaviour.
Atomic Publication in File Processing uses this distinction to separate rename atomicity, fsync durability, directory persistence and NFS visibility.