Linux repositories inspector


February 6, 2018


Manual pages for a GNU/kFreeBSD system


fdatasync, fsync - synchronise changes to a file


.Lb libc


.In unistd.h int fdatasync int fd int fsync int fd


The fsync 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.
The fdatasync system call causes all modified data of fd to be moved to a permanent storage device. Unlike fsync, the system call does not guarantee that file attributes or metadata necessary to access the file are committed to the permanent storage.
The fsync 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.
Both fdatasync and fsync calls are cancellation points.


.Rv -std fsync


The fsync and fdatasync calls fail if:
The fd argument is not a valid descriptor.
The fd argument refers to a socket, not to a file.
[EIO] An I/O error occurred while reading from or writing to the file system.


The fsync system call appeared in BSD 4.2 . The fdatasync system call appeared in
.Fx 11.1 .


The fdatasync system call currently does not guarantee that enqueued aio(4) requests for the file referenced by fd are completed before the syscall returns.
⇧ Top