https://nalar.dev/tags/crash-consistency/ Recent content in Crash Consistency on Nalar Hugo en-us Tue, 15 Sep 2026 00:00:00 +0700 https://nalar.dev/atomic-rename-separates-visibility-from-crash-durability/ Tue, 15 Sep 2026 00:00:00 +0700 https://nalar.dev/atomic-rename-separates-visibility-from-crash-durability/ <p>A successful <code>rename()</code> can replace an existing pathname without exposing an interval in which that destination name is absent. That visibility property makes rename a common publication boundary for configuration files, checkpoints, manifests, and other file-backed state. It does not, by itself, establish that the replacement survives an abrupt loss of power.</p> <p>The distinction is between namespace atomicity and persistence. Atomic replacement constrains what concurrent observers can see while the system is running. Crash durability concerns which writes and metadata changes are guaranteed to remain after volatile state disappears. Treating those properties as equivalent creates a gap precisely at the failure boundary that atomic replacement is often intended to protect.</p>