From: David Masover <ninja@slaphack.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Bryan Henderson <hbryan@us.ibm.com>, Ric Wheeler <ric@emc.com>,
Al Boldi <a1426z@gawab.com>, Chris Wedgwood <cw@f00f.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@oss.sgi.com,
Steve Lord <lord@xfs.org>, 'Nathan Scott' <nathans@sgi.com>,
reiserfs-list@namesys.com
Subject: Re: XFS corruption during power-blackout
Date: Fri, 01 Jul 2005 16:39:25 -0500 [thread overview]
Message-ID: <42C5B80D.2050100@slaphack.com> (raw)
In-Reply-To: <20050701211006.GA13311@wohnheim.fh-wedel.de>
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-07-01 21:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050629001847.GB850@frodo>
2005-06-29 4:53 ` XFS corruption during power-blackout Al Boldi
2005-06-29 16:38 ` Christian Rice
2005-06-29 17:02 ` Chris Wedgwood
2005-06-29 17:56 ` Steve Lord
2005-06-29 20:56 ` Chris Wedgwood
2005-06-30 16:30 ` Bryan Henderson
2005-06-30 18:46 ` Chris Wedgwood
2005-06-30 19:44 ` Jörn Engel
2005-06-30 20:32 ` Chris Wedgwood
2005-06-30 21:07 ` Jörn Engel
2005-07-01 12:36 ` Ric Wheeler
2005-07-01 12:56 ` Jens Axboe
2005-06-30 20:49 ` Bryan Henderson
2005-07-01 12:53 ` Ric Wheeler
2005-07-01 18:24 ` Bryan Henderson
2005-07-01 19:58 ` David Masover
2005-07-01 21:10 ` Jörn Engel
2005-07-01 21:39 ` David Masover [this message]
2005-07-01 1:09 ` Stewart Smith
2005-07-05 15:53 ` Sonny Rao
2005-06-29 21:10 ` Nathan Scott
2005-07-01 8:17 ` David Masover
2005-07-01 9:24 ` Jens Axboe
[not found] ` <20050701131950.GA15180@ime.usp.br>
2005-07-01 13:57 ` Ric Wheeler
2005-07-01 18:37 ` Bryan Henderson
2005-07-01 18:41 ` Jens Axboe
2005-07-11 12:53 ` Ric Wheeler
2005-07-01 14:05 ` Al Boldi
2005-07-01 16:35 ` Alistair John Strachan
2005-07-05 15:49 ` Sonny Rao
2005-07-05 17:25 ` Al Boldi
2005-07-05 18:10 ` Sonny Rao
2005-07-05 19:24 ` Dieter Nützel
2005-07-06 4:24 ` Al Boldi
2005-07-06 4:46 ` Nathan Scott
2005-07-16 7:02 Al Boldi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42C5B80D.2050100@slaphack.com \
--to=ninja@slaphack.com \
--cc=a1426z@gawab.com \
--cc=cw@f00f.org \
--cc=hbryan@us.ibm.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@xfs.org \
--cc=nathans@sgi.com \
--cc=reiserfs-list@namesys.com \
--cc=ric@emc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).