Lines Matching refs:fsync

789 The fsync(2) system call ensures that the data and metadata of a file
793 Without an fsync(2) call, there is no guarantee that the observed
801 ordering on storing changes without explicit fsync(2) calls, in case
804 experience, overlayfs calls fsync(2) on the upper file before completing
807 By default, overlayfs does not explicitly call fsync(2) on copied up
809 persist the user's modification unless the user calls fsync(2).
810 The fsync during copy up only guarantees that if a copy up is observed
815 fsync on a file also persists the parent directory changes, because they
821 to the underlying upper layer.  This is controlled by the "fsync" mount
825     Call fsync(2) on upper file before completion of data copy up.
826     No explicit fsync(2) on directory or metadata-only copy up.
828     Call fsync(2) on upper file and directories before completion of any
833 [*] The mount option "volatile" is an alias to "fsync=volatile".
847 In order to avoid giving a false sense of safety, the syncfs (and fsync)