{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-12",
  "slug": "statx-write-atomic",
  "term": "STATX_WRITE_ATOMIC",
  "aliases": [],
  "definition": "STATX_WRITE_ATOMIC is a Linux statx request for a file's reported atomic-write size limits and maximum vector count.",
  "note": "Check returned masks before interpreting fields; a requested capability is not necessarily supported. Minimum and maximum sizes are in bytes. Direct-I/O buffer alignment is a separate query, and drive-level limits do not establish the capability of a file. The nonzero stx_atomic_write_unit_max_opt is an optimized size limit, not the validity ceiling; zero uses stx_atomic_write_unit_max.",
  "related": [
    "rwf-atomic",
    "torn-write",
    "direct-io"
  ],
  "citations": [
    {
      "id": "statx",
      "title": "Linux man-pages, statx(2): atomic-write fields and returned masks",
      "url": "https://man7.org/linux/man-pages/man2/statx.2.html",
      "accessed": "2026-10-12"
    },
    {
      "id": "open",
      "title": "Linux man-pages, open(2): O_DIRECT, O_DSYNC and O_SYNC",
      "url": "https://man7.org/linux/man-pages/man2/open.2.html",
      "accessed": "2026-10-12"
    },
    {
      "id": "hesela-atomic",
      "title": "Linux atomic writes: untorn does not mean durable",
      "url": "https://hesela.com/analyses/linux-atomic-writes-durability/",
      "accessed": "2026-10-12"
    }
  ]
}