xfs
[Top] [All Lists]

Re: XFS corruption during power-blackout

To: Jörn Engel <joern@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: XFS corruption during power-blackout
From: David Masover <ninja@xxxxxxxxxxxx>
Date: Fri, 01 Jul 2005 16:39:25 -0500
Cc: Bryan Henderson <hbryan@xxxxxxxxxx>, Ric Wheeler <ric@xxxxxxx>, Al Boldi <a1426z@xxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, Steve Lord <lord@xxxxxxx>, "'Nathan Scott'" <nathans@xxxxxxx>, reiserfs-list@xxxxxxxxxxx
In-reply-to: <20050701211006.GA13311@xxxxxxxxxxxxxxxxxxxx>
References: <OF23DC8299.F6F2200B-ON88257031.005B3A9B-88257031.00650D8F@xxxxxxxxxx> <42C5A06F.40906@xxxxxxxxxxxx> <20050701211006.GA13311@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Jörn Engel wrote:
On Fri, 1 July 2005 14:58:39 -0500, David Masover wrote:

Bryan Henderson wrote:
[...]

What you'd really like is to fsync a multi-file unit of work (transaction) -- and not just among open files. You'd like to open, write, and close 1000 files in a single transaction and then commit that transaction, with no syncing due to timers in the meantime. If you're really greedy, you'd also ask for complete rollback if the system fails before the commit.

Both of these are planned for Reiser4.  Or is it 4.1?


Both are pretty trivial to implement for a tree-based fs like
reiserfs.  Non-trivial is the user interface.  Not sure if sys_reiser
is the answer to that.

It is intended to be, I think. But sys_reiser has been pushed off to 4.1, last I checked.

From the general attitude here, I'm guessing that it should *not* be called sys_reiser. We're already doing the meta-files interface for doing anything we want to do with reiser, which means sys_reiser currently only does two things: allows simultaneous access to lots of small files efficiently (versus open()-ing each of them), and transactions. While the two may or may not belong in the same system call, I don't believe they should be Reiser-specific.


<Prev in Thread] Current Thread [Next in Thread>