Supporting transactions in btrfs
Posted Nov 15, 2009 17:41 UTC (Sun) by
anton (guest, #25547)
Parent article:
Supporting transactions in btrfs
Maybe I missed it, but I have not seen a statement of crash
consistency guarantees for Btrfs. I would like to see that before
transactions, and with good guarantees, because nearly all
applications and users will benefit from that, not just a few.
For those who missed what I consider good crash consistency
guarantees, here it is: The after-crash state represents one of the logical
states of the file system before the crash; not necessarily the
latest, but preferably only a few seconds old (configurable). Concerning
fsync(), I would like at least the option to have that guarantee even
in the presence of fsync() (yes, enabling this option will make
fsync() slow in some cases, but it protects against applications that
use fsync() in the wrong order).
Transactions would be cool if they can be done easily. But it
looks like they cannot be done easily on the file system level, so
maybe this should be left to specialized applications.
(
Log in to post comments)