|FSYNC(2)||System Calls Manual||FSYNC(2)|
— synchronise changes to a file
Standard C Library (libc, -lc)
system call causes all modified data and attributes of the file referenced
by the file descriptor fd to be moved to a permanent
storage device. This normally results in all in-core modified copies of
buffers for the associated file to be written to a disk.
system call causes all modified data of fd to be moved
to a permanent storage device. Unlike
system call does not guarantee that file attributes or metadata necessary to
access the file are committed to the permanent storage.
system call should be used by programs that require a file to be in a known
state, for example, in building a simple transaction facility. If the file
metadata has already been committed, using
fdatasync() can be more efficient than
fsync() calls are cancellation points.
fsync() function returns the
value 0 if successful; otherwise the value -1 is returned and
the global variable errno is set to indicate the
fdatasync() calls fail if:
fsync() system call appeared in
system call appeared in FreeBSD 11.1.
fdatasync() system call currently does
not guarantee that enqueued aio(4) requests for the file
referenced by fd are completed before the syscall
|March 30, 2020||Debian|