IMHO, from having spent a fair amount of time on this, durability is a "fluid" concept, especially on desktop hardware (Microsoft had the right idea when they built Win Update on TxF), so if the data is important enough to worry about it, you should architect the system in a way that the durability of a fildes or drive is irrelevant to the overall system.
I once wrote the Novell NetWare drivers for a SCSI host adapter vendor, and part of Novell’s certification testing was to run I/O heavy tests on a system that would randomly cut power to the drive or the computer and make sure that this did not corrupt things beyond what NetWare could fully recover from.
Hardware vendors like host adapter makers and drive makers wanted Novell certification, so made sure that was possible.
They might also provide settings that sacrificed that for more performance, but they would make sure you could get decent performance using the full durability settings.
By your logic there is no such thing as a guarantee in this world, period. A meteor could crash into Earth and wreck everything.
You're being snarky. That's not allowed in the rules here and it's unkind even if it wasn't.
> By your logic there is no such thing as a guarantee in this world, period.
So what does the guarantee really mean?
That the data will be on disk... as long as the crash isn't too hard? What do you usefully do with this guarantee? How is it better than no guarantee?
It does not mean "we're just writing this superfluous text to clock in extra hours or pass a word count threshold".
Where have I said I thought it was about writing time or a word count? You've imagined that.
A flash device that isn't designed carefully enough could lose multiple megabytes of semi-random sectors if it gets interrupted at the wrong time, as a consequence of giant erase blocks.
By giving instructions to the device that the device understands and provides guarantees for...