xfs
[Top] [All Lists]

Re: XFS corruption during power-blackout

To: Bryan Henderson <hbryan@xxxxxxxxxx>
Subject: Re: XFS corruption during power-blackout
From: David Masover <ninja@xxxxxxxxxxxx>
Date: Fri, 01 Jul 2005 14:58:39 -0500
Cc: 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: <OF23DC8299.F6F2200B-ON88257031.005B3A9B-88257031.00650D8F@xxxxxxxxxx>
References: <OF23DC8299.F6F2200B-ON88257031.005B3A9B-88257031.00650D8F@xxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1
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?

I would like said interface to be able to not necessarily flush to disk right away, though. It should certainly be an option (I'm sure MySQL would use that option), but sometimes you want the performance, especially if there are dozens of these transactions firing all at once -- better to let RAM fill up and then flush them all.


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