tag
4 posts
Understand what sync requests from the operating system, where file-specific modes differ, and why durability needs application-level design.
Distinguish FreeBSD fsync, fdatasync, sync, and user-space flushes, handle I/O errors, and test durability without overstating guarantees.
Separate ext4 metadata recovery from application durability by tracing JBD2 transactions, data modes, fsync boundaries, rename, and crash testing.
Build a crash-conscious Linux file replacement sequence with fsync, same-filesystem rename, directory synchronization, and explicit recovery rules.