{
  "slug": "semantic-trace-playback",
  "term": "Semantic trace playback",
  "aliases": [
    "STP (filesystem evaluation)"
  ],
  "definition": "Semantic trace playback evaluates candidate filesystem policies by transforming recorded I/O and issuing the resulting requests to storage.",
  "note": "Timing-sensitive changes need more than a block trace. STP also records buffer-dirtying activity and application fsync calls. These distinguish synchronization requests from timer- or threshold-triggered writes. [atc05]\n\nA faster replay can justify investigating a policy; it does not establish that an implementation preserves crash recovery or application correctness.",
  "status": "research",
  "advantages": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "limitations": [
    {
      "text": "Unmodeled virtual-memory interactions and radical filesystem redesigns can invalidate the playback approximation.",
      "citationIds": [
        "atc05"
      ]
    }
  ],
  "related": [
    "semantic-block-level-analysis",
    "microbenchmark",
    "fsync",
    "crash-consistency"
  ],
  "citations": [
    {
      "id": "atc05",
      "title": "Prabhakaran, Arpaci-Dusseau and Arpaci-Dusseau. Analysis and Evolution of Journaling File Systems. USENIX ATC 2005, section 2.",
      "url": "https://www.usenix.org/events/usenix05/tech/general/full_papers/prabhakaran/prabhakaran.pdf",
      "accessed": "2026-11-21"
    }
  ],
  "provenance": [
    "Primary-source synthesis of section 2.2; the implementation/correctness distinction is an editorial inference, not a reproduced benchmark."
  ]
}
