Re:How can you trust a disk to write data?
by masklinn on Tuesday February 22, 2022 @08:28AM
(#30427645)
> I don't think this is right.
You can think what you want, the entire thing started from marcan (re)discovering that fsync() on macos only flushes from FS to disk but does not require any guarantee of the disk.
> There are a lot of things that can happen after the "disk" acknowledged the write that are a lot more common than a power failure
Like what, putting a bullet through the SSD?
> especially in a machine with batteries!
Not every machine has a battery. Not every SSD is internal and hooked onto that battery.
> a system that gets its reliability from fsync() cannot in practice offer any more data persistence guarantees than one that doesn't.
So your point of view is what, reliability nihilism where data does not exist and death comes to us all?
You can think what you want, the entire thing started from marcan (re)discovering that fsync() on macos only flushes from FS to disk but does not require any guarantee of the disk.
> There are a lot of things that can happen after the "disk" acknowledged the write that are a lot more common than a power failure
Like what, putting a bullet through the SSD?
> especially in a machine with batteries!
Not every machine has a battery. Not every SSD is internal and hooked onto that battery.
> a system that gets its reliability from fsync() cannot in practice offer any more data persistence guarantees than one that doesn't.
So your point of view is what, reliability nihilism where data does not exist and death comes to us all?