what are the guarantees about what happens if a computer crashes during a write()? is it possible for the file to end up with corrupted data at the end, or is each byte of the write atomic?
-
Seriously, "history file corrupt" is a common zsh complaint for me after a hard shutdown (on several systems) and then I have to open it in vim and nuke the last line full of ^@.
I've seen it with text syslogs too. And of course when it happens to systemd-jourmald binary logs it just craps itself hard and refuses to load them.
-
-
Ah, here we go, some discussion about this with
@tytso. data=ordered only guarantees you won't get *garbage* (e.g. leaked free disk blocks, which is a huge security issue), but you can still get zeroes. https://plus.google.com/+KentonVarda/posts/JDwHfAiLGNQ … -
i told you about how macOS's hardware video decode driver used to allocate vmem for frames without zeroing it, right?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.