Tux3: the other next-generation filesystem
Posted Dec 9, 2008 14:48 UTC (Tue) by rwmj
In reply to: Tux3: the other next-generation filesystem
Parent article: Tux3: the other next-generation filesystem
test test test
This sounds like a nice idea at first, but you're forgetting an essential step: if you have multiple
transactions outstanding, you need some way to combine the results to get a consistent filesystem.
For example, suppose that the yum transaction modified
/etc/motd, and a user
edited this file at the same time (before the yum transaction was committed). What is
the final, consistent value of this file after the transaction?
From DBMSes you can find lots of different strategies to deal with these cases. A non-exhaustive
list might include: Don't permit the second transaction to succeed. Always take the result of the first (or
second) transaction and overwrite the other. Use a merge strategy (and there are many different sorts).
As usual in computer science, there is a whole load of interesting, accessible theory here, which is
being completely ignored. My favorite which is directly relevant here is
to post comments)