Hi Chris. On Wed, Apr 23, 2008 at 08:50:54AM -0400, Chris Mason (chris.mason@xxxxxxxxxx) wrote: > Transaction rollback from a filesystem point of view is a reboot. Real > database style transactions with rollback and isolation from other procs etc > etc are outside the scope of Btrfs. Why rollback is a reboot? With copy-on-write it could be possible to just commit tree state, which was before transaction start, as a current one and thus rollback all changes. Having that possibility from userspace could be a great benefit, since in case of application error it is relly simple to undo all changes. -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
