[ROBUSTNESS] Implement atomic metadata writes (Write-Rename pattern) #17

Open
opened 2026-02-14 21:21:24 +00:00 by thabeta · 0 comments
Owner

The meta::Writer presently writes directly to the destination flist file.

Risk: A system crash or process failure during a write operation will leave a corrupted, partial .fl file on disk.

Proposed Fix: Implement a pattern where the writer writes to a temporary file (e.g., .fl.tmp) and performs an atomic rename to the final destination only after a successful flush.

The `meta::Writer` presently writes directly to the destination flist file. **Risk:** A system crash or process failure during a write operation will leave a corrupted, partial `.fl` file on disk. **Proposed Fix:** Implement a pattern where the writer writes to a temporary file (e.g., `.fl.tmp`) and performs an atomic rename to the final destination only after a successful flush.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
geomind_code/my_fs#17
No description provided.