Tag
crash-consistency
- Aug 12, 2026 Verifying Crash Consistency with Fault Injection Why a crash-consistency claim needs an exhaustive state-space argument rather than a test, how to model a device that loses writes and reorders them, and which failures the method cannot find. memory systems
- Jul 7, 2026 What fsync Guarantees and What It Costs on Real Devices The ordering and durability contracts of fsync, fdatasync, and sync_file_range, how a device cache flush turns them into round trips, and where the guarantee quietly ends. performance engineering
- Jun 26, 2026 Copy-on-Write and Block Shadowing Instead of a Log How never modifying a reachable block replaces journal replay with a root pointer swap, and what the tree-copying cost buys in atomicity. filesystems
- Jan 20, 2026 Power-Loss Protection: What a Controller Must Persist, and When The in-flight state a flash controller holds in volatile memory, the energy budget that keeps it alive long enough to flush, and how recovery reconstructs a mapping table from torn pages. hardware engineering
- Jan 14, 2026 A Completed Write Is Not Yet Durable: Persistence Domains and Ordering Why write and close return long before bytes reach media, how a persistence domain decides what a crash can lose, and why durability, ordering, and atomicity need separate mechanisms. memory systems
- Jul 16, 2025 fsync, fdatasync, and What Survives a Power Loss The durability calls promise different things about data and metadata, and a file entry needs a second call on its directory; where the guarantees stop on each filesystem. filesystems
- Dec 20, 2023 Rename Atomicity and the Replacement of a Directory Entry How rename changes two directory entries without a window of invisibility, which cross-filesystem cases the guarantee excludes, and why the call is the primitive behind atomic file updates. filesystems
- Oct 2, 2023 Write Ordering and the Crash Window Between Metadata Updates Why a filesystem that issues correct writes in the right order can still be corrupt after a power loss, and how ordering constraints, atomicity, and recovery strategies separate. filesystems
- Sep 9, 2023 Boot Metadata Persistence and the Commit Record The record format that survives an interrupted write, how many copies are enough, and why the sequence number rather than the timestamp decides which copy wins. embedded systems