semantic-trace-playback · research · also STP (filesystem evaluation)

Semantic trace playback

Semantic trace playback evaluates candidate filesystem policies by transforming recorded I/O and issuing the resulting requests to storage.

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. [1]

A faster replay can justify investigating a policy; it does not establish that an implementation preserves crash recovery or application correctness.

Relations

related
Semantic block-level analysis, Microbenchmark, fsync, Crash consistency

Limitations

  • Unmodeled virtual-memory interactions and radical filesystem redesigns can invalidate the playback approximation. [1]

Citations

  1. Prabhakaran, Arpaci-Dusseau and Arpaci-Dusseau. Analysis and Evolution of Journaling File Systems. USENIX ATC 2005, section 2. (accessed 2026-11-21)
Sources & caveats
  • Primary-source synthesis of section 2.2; the implementation/correctness distinction is an editorial inference, not a reproduced benchmark.

JSON: /data/terms/semantic-trace-playback.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Semantic trace playback. Hesela. 2026-11-21. https://hesela.dev/terms/semantic-trace-playback/