close-to-open consistency | My Note

close-to-open consistency

Updated: Oct 7th, 2023

close-to-open consistency make that the metadata operation can not accelerate by the client metadata cache. link

It’s a guarantee that when a file is closed subsequent opens will see the latest changes. This is achieved by the client flushing all cached changes to the server when it closes the file, and clients opening a file must ignore all cached info they have about the file. This is as opposed to time-bounded consistency where, even after a file is closed, it may take a period of time before the server and subsequent clients see the changes. highlight

The only consistency guarantee made by NFS is called close-to-open consistency, which means that any changes made by you are flushed to the server on closing the file, and a cache revalidation occurs when you re-open it. highlight

Reference

  1. (4) NFS: What is close-to-open cache consistency? - Quora
  2. https://www.kernel.org/doc/ols/2006/ols2006v2-pages-59-72.pdf
  3. NFS Sucks: Cache Consistency – comphilip

Instead of authenticating the giscus application, you can also comment directly on GitHub.

TOC

Notes mentioning this note

There are no notes linking to this note.