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

# statx(2)

get file status (extended)

## NAME

statx - get file status (extended)

## LIBRARY

Standard C library (*libc*, *-lc*)

## SYNOPSIS

```
#define _GNU_SOURCE          /* See feature_test_macros(7) */
#include <fcntl.h>           /* Definition of AT_* constants */
#include <sys/stat.h>
```

**int statx(int** *dirfd***, const char \*\_Nullable restrict** *path***,**           **int** *flags***, unsigned int** *mask***,**           **struct statx \*restrict** *statxbuf***);**

## DESCRIPTION

This function returns information about a file, storing it in the buffer pointed to by *statxbuf*. The returned buffer is a structure of the following type:

```
struct statx {
    __u32 stx_mask;        /* Mask of bits indicating
                              filled fields */
    __u32 stx_blksize;     /* Block size for filesystem I/O */
    __u64 stx_attributes;  /* Extra file attribute indicators */
    __u32 stx_nlink;       /* Number of hard links */
    __u32 stx_uid;         /* User ID of owner */
    __u32 stx_gid;         /* Group ID of owner */
    __u16 stx_mode;        /* File type and mode */
    __u64 stx_ino;         /* Inode number */
    __u64 stx_size;        /* Total size in bytes */
    __u64 stx_blocks;      /* Number of 512B blocks allocated */
    __u64 stx_attributes_mask;
                           /* Mask to show what's supported
                              in stx_attributes */
    /* The following fields are file timestamps */
    struct statx_timestamp stx_atime;  /* Last access */
    struct statx_timestamp stx_btime;  /* Creation */
    struct statx_timestamp stx_ctime;  /* Last status change */
    struct statx_timestamp stx_mtime;  /* Last modification */
    /* If this file represents a device, then the next two
       fields contain the ID of the device */
    __u32 stx_rdev_major;  /* Major ID */
    __u32 stx_rdev_minor;  /* Minor ID */
    /* The next two fields contain the ID of the device
       containing the filesystem where the file resides */
    __u32 stx_dev_major;   /* Major ID */
    __u32 stx_dev_minor;   /* Minor ID */
    __u64 stx_mnt_id;      /* Mount ID */
    /* Direct I/O alignment restrictions */
    __u32 stx_dio_mem_align;
    __u32 stx_dio_offset_align;
    __u64 stx_subvol;      /* Subvolume identifier */
    /* Direct I/O atomic write limits */
    __u32 stx_atomic_write_unit_min;
    __u32 stx_atomic_write_unit_max;
    __u32 stx_atomic_write_segments_max;
    /* File offset alignment for direct I/O reads */
    __u32 stx_dio_read_offset_align;
    /* Direct I/O atomic write max opt limit */
    __u32 stx_atomic_write_unit_max_opt;
};
```

The file timestamps are structures of the following type:

```
struct statx_timestamp {
    __s64 tv_sec;    /* Seconds since the Epoch (UNIX time) */
    __u32 tv_nsec;   /* Nanoseconds since tv_sec */
};
```

(Note that reserved space and padding is omitted.)

### Invoking statx():

To access a file's status, no permissions are required on the file itself, but in the case of **statx**() with a pathname, execute (search) permission is required on all of the directories in *path* that lead to the file.

**statx**() uses *path*, *dirfd*, and *flags* to identify the target file in one of the following ways:

- An absolute pathname

  If *path* begins with a slash, then it is an absolute pathname that identifies the target file. In this case, *dirfd* is ignored.

- A relative pathname

  If *path* is a string that begins with a character other than a slash and *dirfd* is **AT\_FDCWD**, then *path* is a relative pathname that is interpreted relative to the process's current working directory.

- A directory-relative pathname

  If *path* is a string that begins with a character other than a slash and *dirfd* is a file descriptor that refers to a directory, then *path* is a relative pathname that is interpreted relative to the directory referred to by *dirfd*. (See [**openat**(2)](/openat/2.md) for an explanation of why this is useful.)

- By file descriptor

  If *path* is an empty string (or NULL since Linux 6.11) and the **AT\_EMPTY\_PATH** flag is specified in *flags* (see below), then the target file is the one referred to by the file descriptor *dirfd*.

*flags* can be used to influence a pathname-based lookup. A value for *flags* is constructed by ORing together zero or more of the following constants:

- **AT\_EMPTY\_PATH**

  If *path* is an empty string (or NULL since Linux 6.11), operate on the file referred to by *dirfd* (which may have been obtained using the [**open**(2)](/open/2.md) **O\_PATH** flag). In this case, *dirfd* can refer to any type of file, not just a directory.

-

  If *dirfd* is **AT\_FDCWD**, the call operates on the current working directory.

- **AT\_NO\_AUTOMOUNT**

  Don't automount the terminal ("basename") component of *path* if it is a directory that is an automount point. This allows the caller to gather attributes of an automount point (rather than the location it would mount). This flag has no effect if the mount point has already been mounted over.

-

  The **AT\_NO\_AUTOMOUNT** flag can be used in tools that scan directories to prevent mass-automounting of a directory of automount points.

-

  All of [**stat**(2)](/stat/2.md), [**lstat**(2)](/lstat/2.md), and [**fstatat**(2)](/fstatat/2.md) act as though **AT\_NO\_AUTOMOUNT** was set.

- **AT\_SYMLINK\_NOFOLLOW**

  If *path* is a symbolic link, do not dereference it: instead return information about the link itself, like [**lstat**(2)](/lstat/2.md).

*flags* can also be used to control what sort of synchronization the kernel will do when querying a file on a remote filesystem. This is done by ORing in one of the following values:

- **AT\_STATX\_SYNC\_AS\_STAT**

  Do whatever [**stat**(2)](/stat/2.md) does. This is the default and is very much filesystem-specific.

- **AT\_STATX\_FORCE\_SYNC**

  Force the attributes to be synchronized with the server. This may require that a network filesystem perform a data writeback to get the timestamps correct.

- **AT\_STATX\_DONT\_SYNC**

  Don't synchronize anything, but rather just take whatever the system has cached if possible. This may mean that the information returned is approximate, but, on a network filesystem, it may not involve a round trip to the server - even if no lease is held.

The *mask* argument to **statx**() is used to tell the kernel which fields the caller is interested in. *mask* is an ORed combination of the following constants:

| | |
| --- | --- |
| **STATX\_TYPE** | Want stx\_mode & S\_IFMT |
| **STATX\_MODE** | Want stx\_mode & ~S\_IFMT |
| **STATX\_NLINK** | Want stx\_nlink |
| **STATX\_UID** | Want stx\_uid |
| **STATX\_GID** | Want stx\_gid |
| **STATX\_ATIME** | Want stx\_atime |
| **STATX\_MTIME** | Want stx\_mtime |
| **STATX\_CTIME** | Want stx\_ctime |
| **STATX\_INO** | Want stx\_ino |
| **STATX\_SIZE** | Want stx\_size |
| **STATX\_BLOCKS** | Want stx\_blocks |
| **STATX\_BASIC\_STATS** | \[All of the above\] |
| **STATX\_BTIME** | Want stx\_btime |
| **STATX\_ALL** | The same as STATX\_BASIC\_STATS \| STATX\_BTIME. |
|  | It is deprecated and should not be used. |
| **STATX\_MNT\_ID** | Want stx\_mnt\_id (since Linux 5.8) |
| **STATX\_DIOALIGN** | Want stx\_dio\_mem\_align and stx\_dio\_offset\_align. |
|  | (since Linux 6.1; support varies by filesystem) |
| **STATX\_MNT\_ID\_UNIQUE** | Want unique stx\_mnt\_id (since Linux 6.8) |
| **STATX\_SUBVOL** | Want stx\_subvol |
|  | (since Linux 6.10; support varies by filesystem) |
| **STATX\_WRITE\_ATOMIC** | Want stx\_atomic\_write\_unit\_min, |
|  | stx\_atomic\_write\_unit\_max, |
|  | stx\_atomic\_write\_segments\_max, |
|  | and stx\_atomic\_write\_unit\_max\_opt. |
|  | (since Linux 6.11; support varies by filesystem) |
| **STATX\_DIO\_READ\_ALIGN** | Want stx\_dio\_read\_offset\_align. |
|  | (since Linux 6.14; support varies by filesystem) |

Note that, in general, the kernel does *not* reject values in *mask* other than the above. (For an exception, see **EINVAL** in errors.) Instead, it simply informs the caller which values are supported by this kernel and filesystem via the *statx.stx\_mask* field. Therefore, *do not* simply set *mask* to **UINT\_MAX** (all bits set), as one or more bits may, in the future, be used to specify an extension to the buffer.

### The returned information

The status information for the target file is returned in the *statx* structure pointed to by *statxbuf*. Included in this is *stx\_mask* which indicates what other information has been returned. *stx\_mask* has the same format as the *mask* argument and bits are set in it to indicate which fields have been filled in.

It should be noted that the kernel may return fields that weren't requested and may fail to return fields that were requested, depending on what the backing filesystem supports. (Fields that are given values despite being unrequested can just be ignored.) In either case, *stx\_mask* will not be equal *mask*.

If a filesystem does not support a field or if it has an unrepresentable value (for instance, a file with an exotic type), then the mask bit corresponding to that field will be cleared in *stx\_mask* even if the user asked for it and a dummy value will be filled in for compatibility purposes if one is available (e.g., a dummy UID and GID may be specified to mount under some circumstances).

A filesystem may also fill in fields that the caller didn't ask for if it has values for them available and the information is available at no extra cost. If this happens, the corresponding bits will be set in *stx\_mask*.

*Note*: for performance and simplicity reasons, different fields in the *statx* structure may contain state information from different moments during the execution of the system call. For example, if *stx\_mode* or *stx\_uid* is changed by another process by calling [**chmod**(2)](/chmod/2.md) or [**chown**(2)](/chown/2.md), **stat**() might return the old *stx\_mode* together with the new *stx\_uid*, or the old *stx\_uid* together with the new *stx\_mode*.

Apart from *stx\_mask* (which is described above), the fields in the *statx* structure are:

- *stx\_blksize*

  The "preferred" block size for efficient filesystem I/O. (Writing to a file in smaller chunks may cause an inefficient read-modify-rewrite.)

- *stx\_attributes*

  Further status information about the file (see below for more information).

- *stx\_nlink*

  The number of hard links on a file.

- *stx\_uid*

  This field contains the user ID of the owner of the file.

- *stx\_gid*

  This field contains the ID of the group owner of the file.

- *stx\_mode*

  The file type and mode. See [**inode**(7)](/inode/7.md) for details.

- *stx\_ino*

  The inode number of the file.

- *stx\_size*

  The size of the file (if it is a regular file or a symbolic link) in bytes. The size of a symbolic link is the length of the pathname it contains, without a terminating null byte.

- *stx\_blocks*

  The number of blocks allocated to the file on the medium, in 512-byte units. (This may be smaller than *stx\_size*/512 when the file has holes.)

- *stx\_attributes\_mask*

  A mask indicating which bits in *stx\_attributes* are supported by the VFS and the filesystem.

- *stx\_atime*

  The file's last access timestamp.

- *stx\_btime*

  The file's creation timestamp.

- *stx\_ctime*

  The file's last status change timestamp.

- *stx\_mtime*

  The file's last modification timestamp.

- *stx\_dev\_major* *stx\_dev\_minor*

  The device on which this file (inode) resides.

- *stx\_rdev\_major* *stx\_rdev\_minor*

  The device that this file (inode) represents if the file is of block or character device type.

- *stx\_mnt\_id*

  If using STATX\_MNT\_ID, this is the mount ID of the mount containing the file. This is the same number reported by [**name\_to\_handle\_at**(2)](/name_to_handle_at/2.md) and corresponds to the number in the first field in one of the records in */proc/self/mountinfo*.

-

  If using STATX\_MNT\_ID\_UNIQUE, this is the unique mount ID of the mount containing the file. This is the number reported by [**listmount**(2)](/listmount/2.md) and is the ID used to query the mount with [**statmount**(2)](/statmount/2.md)**.** It is guaranteed to not be reused while the system is running.

- *stx\_dio\_mem\_align*

  The alignment (in bytes) required for user memory buffers for direct I/O (**O\_DIRECT**) on this file, or 0 if direct I/O is not supported on this file.

-

  **STATX\_DIOALIGN** (*stx\_dio\_mem\_align* and *stx\_dio\_offset\_align*) is supported on block devices since Linux 6.1. The support on regular files varies by filesystem; it is supported by ext4, f2fs, and xfs since Linux 6.1.

- *stx\_dio\_offset\_align*

  The alignment (in bytes) required for file offsets and I/O segment lengths for direct I/O (**O\_DIRECT**) on this file, or 0 if direct I/O is not supported on this file. This will only be nonzero if *stx\_dio\_mem\_align* is nonzero, and vice versa.

- *stx\_dio\_read\_offset\_align*

  The alignment (in bytes) required for file offsets and I/O segment lengths for direct I/O reads (**O\_DIRECT**) on this file. If zero, the limit in *stx\_dio\_offset\_align* applies for reads as well. If non-zero, this value must be smaller than or equal to *stx\_dio\_offset\_align* which must be provided by the file system if requested by the application. The memory alignment in *stx\_dio\_mem\_align* is not affected by this value.

-

  **STATX\_DIO\_READ\_ALIGN** (*stx\_dio\_offset\_align*) is supported by xfs on regular files since Linux 6.14.

- *stx\_subvol*

  Subvolume number of the current file.

-

  Subvolumes are fancy directories, i.e., they form a tree structure that may be walked recursively. Support varies by filesystem; it is supported by bcachefs and btrfs since Linux 6.10.

- *stx\_atomic\_write\_unit\_min* *stx\_atomic\_write\_unit\_max*

  The minimum and maximum sizes (in bytes) supported for direct I/O (**O\_DIRECT**) on the file to be written with torn-write protection. These values are each guaranteed to be a power-of-2.

-

  **STATX\_WRITE\_ATOMIC** (*stx\_atomic\_write\_unit\_min*, *stx\_atomic\_write\_unit\_max*, and *stx\_atomic\_write\_segments\_max*) is supported on block devices since Linux 6.11. The support on regular files varies by filesystem; it is supported by xfs and ext4 since Linux 6.13.

- *stx\_atomic\_write\_unit\_max\_opt*

  The maximum size (in bytes) which is optimised for writes issued with torn-write protection. If non-zero, this value will not exceed the value in *stx\_atomic\_write\_unit\_max* and will not be less than the value in *stx\_atomic\_write\_unit\_min*. A value of zero indicates that *stx\_atomic\_write\_unit\_max* is the optimised limit. Slower writes may be experienced when the size of the write exceeds *stx\_atomic\_write\_unit\_max\_opt* (when non-zero).

- *stx\_atomic\_write\_segments\_max*

  The maximum number of elements in an array of vectors for a write with torn-write protection enabled. See **RWF\_ATOMIC** flag for [**pwritev2**(2)](/pwritev2/2.md).

For further information on the above fields, see [**inode**(7)](/inode/7.md).

### File attributes

The *stx\_attributes* field contains a set of ORed flags that indicate additional attributes of the file. Note that any attribute that is not indicated as supported by *stx\_attributes\_mask* has no usable value here. The bits in *stx\_attributes\_mask* correspond bit-by-bit to *stx\_attributes*.

The flags are as follows:

- **STATX\_ATTR\_COMPRESSED**

  The file is compressed by the filesystem and may take extra resources to access.

- **STATX\_ATTR\_IMMUTABLE**

  The file cannot be modified: it cannot be deleted or renamed, no hard links can be created to this file and no data can be written to it. See [**chattr**(1)](/chattr/1.md).

- **STATX\_ATTR\_APPEND**

  The file can only be opened in append mode for writing. Random access writing is not permitted. See [**chattr**(1)](/chattr/1.md).

- **STATX\_ATTR\_NODUMP**

  File is not a candidate for backup when a backup program such as [**dump**(8)](/dump/8.md) is run. See [**chattr**(1)](/chattr/1.md).

- **STATX\_ATTR\_ENCRYPTED**

  A key is required for the file to be encrypted by the filesystem.

- **STATX\_ATTR\_VERITY** (since Linux 5.5)

  The file has fs-verity enabled. It cannot be written to, and all reads from it will be verified against a cryptographic hash that covers the entire file (e.g., via a Merkle tree).

- **STATX\_ATTR\_WRITE\_ATOMIC** (since Linux 6.11)

  The file supports torn-write protection.

- **STATX\_ATTR\_DAX** (since Linux 5.8)

  The file is in the DAX (cpu direct access) state. DAX state attempts to minimize software cache effects for both I/O and memory mappings of this file. It requires a file system which has been configured to support DAX.

-

  DAX generally assumes all accesses are via CPU load / store instructions which can minimize overhead for small accesses, but may adversely affect CPU utilization for large transfers.

-

  File I/O is done directly to/from user-space buffers and memory mapped I/O may be performed with direct memory mappings that bypass the kernel page cache.

-

  While the DAX property tends to result in data being transferred synchronously, it does not give the same guarantees as the **O\_SYNC** flag (see [**open**(2)](/open/2.md)), where data and the necessary metadata are transferred together.

-

  A DAX file may support being mapped with the **MAP\_SYNC** flag, which enables a program to use CPU cache flush instructions to persist CPU store operations without an explicit [**fsync**(2)](/fsync/2.md). See [**mmap**(2)](/mmap/2.md) for more information.

- **STATX\_ATTR\_MOUNT\_ROOT** (since Linux 5.8)

  The file is the root of a mount.

## RETURN VALUE

On success, zero is returned. On error, -1 is returned, and *errno* is set to indicate the error.

## ERRORS

- **EACCES**

  Search permission is denied for one of the directories in the path prefix of *path*. (See also [**path\_resolution**(7)](/path_resolution/7.md).)

- **EBADF**

  *path* is relative but *dirfd* is neither **AT\_FDCWD** nor a valid file descriptor.

- **EFAULT**

  *path* or *statxbuf* points to a location outside the process's accessible address space or is NULL (except since Linux 6.11 if **AT\_EMPTY\_PATH** is specified in *flags*, *path* is allowed to be NULL).

- **EINVAL**

  Invalid flag specified in *flags*.

- **EINVAL**

  Reserved flag specified in *mask*. (Currently, there is one such flag, designated by the constant **STATX\_\_RESERVED**, with the value 0x80000000U.)

- **ELOOP**

  Too many symbolic links encountered while traversing the pathname.

- **ENAMETOOLONG**

  *path* is too long.

- **ENOENT**

  A component of *path* does not exist, or *path* is an empty string and **AT\_EMPTY\_PATH** was not specified in *flags*.

- **ENOMEM**

  Out of memory (i.e., kernel memory).

- **ENOTDIR**

  A component of the path prefix of *path* is not a directory or *path* is relative and *dirfd* is a file descriptor referring to a file other than a directory.

## STANDARDS

Linux.

## HISTORY

Linux 4.11, glibc 2.28.

## SEE ALSO

[**ls**(1)](/ls/1.md), [**stat**(1)](/stat/1.md), [**access**(2)](/access/2.md), [**chmod**(2)](/chmod/2.md), [**chown**(2)](/chown/2.md), [**name\_to\_handle\_at**(2)](/name_to_handle_at/2.md), [**readlink**(2)](/readlink/2.md), [**stat**(2)](/stat/2.md), [**utime**(2)](/utime/2.md), [**proc**(5)](/proc/5.md), [**capabilities**(7)](/capabilities/7.md), [**inode**(7)](/inode/7.md), [**symlink**(7)](/symlink/7.md)
