aio_fsync(3) [netbsd man page]

AIO_FSYNC(3)						   BSD Library Functions Manual 					      AIO_FSYNC(3)

NAME

     aio_fsync -- asynchronous data synchronization of file (REALTIME)

LIBRARY

     POSIX Real-time Library (librt, -lrt)

SYNOPSIS

     #include <aio.h>

     int
     aio_fsync(int op, struct aiocb *aiocbp);

DESCRIPTION

     The aio_fsync() system call allows the calling process to force all modified data associated with the file descriptor aiocbp->aio_fildes to
     be flushed to the stable storage device.  The call returns immediately after the synchronization request has been enqueued to the descriptor;
     the synchronization may or may not have completed at the time the call returns.  If the request could not be enqueued, generally due to
     invalid arguments, the call returns without having enqueued the request.

     The op argument could be set only to O_DSYNC or O_SYNC.  If op is O_DSYNC, then aio_fsync() does the same as a fdatasync() call, if O_SYNC,
     then the same as fsync().

     If _POSIX_PRIORITIZED_IO is defined, and the descriptor supports it, then the enqueued operation is submitted at a priority equal to that of
     the calling process minus aiocbp->aio_reqprio.

     The aiocbp pointer may be subsequently used as an argument to aio_return() and aio_error() in order to determine return or error status for
     the enqueued operation while it is in progress.

RETURN VALUES

     The aio_fsync() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The aio_fsync() system call will fail if:

     [EAGAIN]		The request was not queued because of system resource limitations.

     The following conditions may be synchronously detected when the aio_fsync() system call is made, or asynchronously, at any time thereafter.
     If they are detected at call time, aio_fsync() returns -1 and sets errno appropriately; otherwise the aio_return() system call must be
     called, and will return -1, and aio_error() must be called to determine the actual value that would have been returned in errno.

     [EBADF]		The aiocbp->aio_fildes is invalid for writing.

     [EINVAL]		This implementation does not support synchronized I/O for this file, or the op argument is neither set to O_DSYNC nor
			O_SYNC.

SEE ALSO

     fcntl(2), fdatasync(2), fsync(2), aio(3)

STANDARDS

     The aio_fsync() system call is expected to conform to the IEEE Std 1003.1-2001 (``POSIX.1'') standard.

HISTORY

     The aio_fsync() system call first appeared in NetBSD 5.0.

BSD
								   May 17, 2010 							       BSD

AIO_FSYNC(2)						      BSD System Calls Manual						      AIO_FSYNC(2)

NAME

     aio_fsync -- asynchronous file synchronization (REALTIME)

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <aio.h>

     int
     aio_fsync(int op, struct aiocb *iocb);

DESCRIPTION

     The aio_fsync() system call allows the calling process to move all modified data associated with the descriptor iocb->aio_fildes to a perma-
     nent storage device.  The call returns immediately after the synchronization request has been enqueued to the descriptor; the synchronization
     may or may not have completed at the time the call returns.

     The op argument can only be set to O_SYNC to cause all currently queued I/O operations to be completed as if by a call to fsync(2).

     If _POSIX_PRIORITIZED_IO is defined, and the descriptor supports it, then the enqueued operation is submitted at a priority equal to that of
     the calling process minus iocb->aio_reqprio.

     The iocb pointer may be subsequently used as an argument to aio_return() and aio_error() in order to determine return or error status for the
     enqueued operation while it is in progress.

     If the request could not be enqueued (generally due to invalid arguments), the call returns without having enqueued the request.

RETURN VALUES

     The aio_fsync() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The aio_fsync() system call will fail if:

     [EAGAIN]		The request was not queued because of system resource limitations.

     [ENOSYS]		The aio_fsync() system call is not supported.

     [EINVAL]		A value of the op argument is not set to O_SYNC.

     The following conditions may be synchronously detected when the aio_fsync() system call is made, or asynchronously, at any time thereafter.
     If they are detected at call time, aio_fsync() returns -1 and sets errno appropriately; otherwise the aio_return() system call must be
     called, and will return -1, and aio_error() must be called to determine the actual value that would have been returned in errno.

     [EBADF]		The iocb->aio_fildes argument is not a valid descriptor.

     [EINVAL]		This implementation does not support synchronized I/O for this file.

     If the request is successfully enqueued, but subsequently cancelled or an error occurs, the value returned by the aio_return() system call is
     per the read(2) and write(2) system calls, and the value returned by the aio_error() system call is one of the error returns from the read(2)
     or write(2) system calls.

SEE ALSO

     aio_cancel(2), aio_error(2), aio_read(2), aio_return(2), aio_suspend(2), aio_waitcomplete(2), aio_write(2), fsync(2), siginfo(3), aio(4)

STANDARDS

     The aio_fsync() system call is expected to conform to the IEEE Std 1003.1 (``POSIX.1'') standard.

HISTORY

     The aio_fsync() system call first appeared in FreeBSD 7.0.

BSD
								 December 27, 2013							       BSD