Messages in this thread | | | Date | Tue, 26 Apr 2005 17:12:31 +0200 | From | Lars Marowsky-Bree <> | Subject | Re: filesystem transactions API |
| |
On 2005-04-26T11:01:54, John Stoffel <john@stoffel.org> wrote:
> Jamie> No. A transaction means that _all_ processes will see the > Jamie> whole transaction or not. > This is really hard. How do you handle the case where process X > starts a transaction modifies files a, b & c, but process Y has file b > open for writing, and never lets it go? Or the file gets unlinked?
I suggest you ask Hans, reiser4 does have such a feature if I recall correctly.
It gets a whole lot more interesting if you want the sucker to spawn more than one mount though.
Sincerely, Lars Marowsky-Brée <lmb@suse.de>
-- High Availability & Clustering SUSE Labs, Research and Development SUSE LINUX Products GmbH - A Novell Business
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |