On Sat, Jan 8, 2011 at 10:43 PM, Thomas Bellman <bell...@nsc.liu.se> wrote: > So, basically database transactions with an isolation level of > "committed read", for file operations. That's something I have > wanted for a long time, especially if I also get a rollback() > operation, but have never heard of any Unix that implemented it.
True, that's why this feature request is here. Note that it's (ATM) only about single file data replace. > A separate commit() operation would be better than conflating it > with close(). And as I said, we want a rollback() as well. And > a process that terminates without committing the transaction that > it is performing, should have the transaction automatically rolled > back. What could you do between commit and close? > I only have a very shallow knowledge about the internals of the > Linux kernel in regards to filesystems, but I suspect that this > could be implemented almost entirely within the VFS, and not need > to touch the actual filesystems, as long as you are satisfied > with a limited amount of transaction space (what fits in RAM + > swap). > > I'm looking forward to your implementation. :-) Even though I > suspect that it would be a rather large undertaking to implement... I have no plans to work on an implementation. -- Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
