{
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-20",
  "slug": "advfs-syncv",
  "term": "AdvFS syncv",
  "aliases": [
    "syncv (AdvFS)"
  ],
  "definition": "AdvFS syncv is a filesystem-specific operation that commits updates to several O_ATOMIC files as one failure-atomic bundle.",
  "note": "The FAST 2015 design uses a journal transaction to commit clone-deletion metadata. Applications must coordinate concurrent file access. It is distinct from Linux RWF_ATOMIC, syncfs and an ordinary sequence of fsync calls.",
  "related": [
    "rwf-atomic",
    "fsync",
    "syncfs",
    "crash-consistency",
    "copy-on-write"
  ],
  "provenance": [
    "Historical interface; current availability is not established."
  ],
  "citations": [
    {
      "id": "advfs-fast15",
      "title": "Verma et al., Failure-Atomic Updates of Application Data in a Linux File System, FAST 2015, pp. 203-211, sections 3-4.",
      "url": "https://www.usenix.org/system/files/conference/fast15/fast15-paper-verma.pdf",
      "accessed": "2026-10-20"
    },
    {
      "id": "hesela-atomic",
      "title": "Linux atomic writes: untorn does not mean durable",
      "url": "https://hesela.com/analyses/linux-atomic-writes-durability/#syncv-budget",
      "accessed": "2026-10-20"
    }
  ]
}