{
  "slug": "ext4-data-ordered",
  "term": "Ext4 ordered mode",
  "aliases": [
    "ext4 data=ordered"
  ],
  "definition": "Ext4 ordered mode journals metadata and orders associated file-data writes before the metadata transaction commits.",
  "note": "The default data=ordered mode does not put ordinary file contents in the journal or make them application-atomic. Fast commits are also scoped to ordered mode in the reviewed design. [journal]\n\nIn Linux v6.12, ext4_map_blocks registers newly allocated visible blocks for ordered-data handling, excluding unwritten or explicitly zeroed mappings in that branch. This is not a global ordering guarantee for every overwrite. [ordered-code]",
  "related": [
    "ext4-data-journal",
    "ext4-data-writeback",
    "ext4-auto-da-alloc",
    "ext4-fast-commit",
    "persistence-ordering",
    "unwritten-extent"
  ],
  "citations": [
    {
      "id": "journal",
      "title": "Linux v6.12: journal coverage and ordered-mode fast commits",
      "url": "https://github.com/torvalds/linux/blob/adc218676eef25575469234709c2d87185ca223a/Documentation/filesystems/ext4/journal.rst",
      "accessed": "2026-10-21"
    },
    {
      "id": "ordered-code",
      "title": "Linux v6.12: ext4_map_blocks ordered-data registration",
      "url": "https://github.com/torvalds/linux/blob/adc218676eef25575469234709c2d87185ca223a/fs/ext4/inode.c#L657-L682",
      "accessed": "2026-10-21"
    }
  ],
  "provenance": [
    "Source review scoped to Linux v6.12; not a crash experiment or certification of later kernels."
  ],
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-21"
}