---
name: "aio_write"
section: "3"
platform: "linux"
package: "man-pages"
version: "6.19-1"
release: "Arch Linux 2026-11-01"
platforms: ["linux"]
url: "https://new.carta.tech/aio_write/3"
---

# aio\_write(3)

asynchronous write

## NAME

aio\_write - asynchronous write

## LIBRARY

Real-time library (*librt*, *-lrt*)

## SYNOPSIS

```
#include <aio.h>
```

**int aio\_write(struct aiocb \****aiocbp***);**

## DESCRIPTION

The **aio\_write**() function queues the I/O request described by the buffer pointed to by *aiocbp*. This function is the asynchronous analog of [**write**(2)](/write/2.md). The arguments of the call

```
write(fd, buf, count)
```

correspond (in order) to the fields *aio\_fildes*, *aio\_buf*, and *aio\_nbytes* of the structure pointed to by *aiocbp*. (See [**aio**(7)](/aio/7.md) for a description of the *aiocb* structure.)

If **O\_APPEND** is not set, the data is written starting at the absolute position *aiocbp-\>aio\_offset*, regardless of the file offset. If **O\_APPEND** is set, data is written at the end of the file in the same order as **aio\_write**() calls are made. After the call, the value of the file offset is unspecified.

The "asynchronous" means that this call returns as soon as the request has been enqueued; the write may or may not have completed when the call returns. One tests for completion using [**aio\_error**(3)](/aio_error/3.md). The return status of a completed I/O operation can be obtained [**aio\_return**(3)](/aio_return/3.md). Asynchronous notification of I/O completion can be obtained by setting *aiocbp-\>aio\_sigevent* appropriately; see [**sigevent**(3type)](/sigevent/3type.md) for details.

If **\_POSIX\_PRIORITIZED\_IO** is defined, and this file supports it, then the asynchronous operation is submitted at a priority equal to that of the calling process minus *aiocbp-\>aio\_reqprio*.

The field *aiocbp-\>aio\_lio\_opcode* is ignored.

No data is written to a regular file beyond its maximum offset.

## RETURN VALUE

On success, 0 is returned. On error, the request is not enqueued, -1 is returned, and *errno* is set to indicate the error. If an error is detected only later, it will be reported via [**aio\_return**(3)](/aio_return/3.md) (returns status -1) and [**aio\_error**(3)](/aio_error/3.md) (error status—whatever one would have gotten in *errno*, such as **EBADF**).

## ERRORS

- **EAGAIN**

  Out of resources.

- **EBADF**

  *aio\_fildes* is not a valid file descriptor open for writing.

- **EFBIG**

  The file is a regular file, we want to write at least one byte, but the starting position is at or beyond the maximum offset for this file.

- **EINVAL**

  One or more of *aio\_offset*, *aio\_reqprio*, *aio\_nbytes* are invalid.

- **ENOSYS**

  **aio\_write**() is not implemented.

## ATTRIBUTES

For an explanation of the terms used in this section, see [**attributes**(7)](/attributes/7.md).

| | | |
| --- | --- | --- |
| **Interface** | **Attribute** | **Value** |
| **aio\_write**() | Thread safety | MT-Safe |

## STANDARDS

POSIX.1-2008.

## HISTORY

glibc 2.1. POSIX.1-2001.

## NOTES

It is a good idea to zero out the control block before use. The control block must not be changed while the write operation is in progress. The buffer area being written out must not be accessed during the operation or undefined results may occur. The memory areas involved must remain valid.

Simultaneous I/O operations specifying the same *aiocb* structure produce undefined results.

## SEE ALSO

[**aio\_cancel**(3)](/aio_cancel/3.md), [**aio\_error**(3)](/aio_error/3.md), [**aio\_fsync**(3)](/aio_fsync/3.md), [**aio\_read**(3)](/aio_read/3.md), [**aio\_return**(3)](/aio_return/3.md), [**aio\_suspend**(3)](/aio_suspend/3.md), [**lio\_listio**(3)](/lio_listio/3.md), [**aio**(7)](/aio/7.md)