From: Hans Reiser <reiser@namesys.com>
To: Tom Vier <tmv@comcast.net>
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: reiser4 data journalling?
Date: Fri, 29 Aug 2003 04:21:01 +0400 [thread overview]
Message-ID: <3F4E9C6D.2080009@namesys.com> (raw)
In-Reply-To: <20030829001814.GB9019@zero>
Tom Vier wrote:
>On Fri, Aug 29, 2003 at 12:48:36AM +0400, Hans Reiser wrote:
>
>
>>full data journaling means that if you perform writes that are 4k or
>>less, and page align them, they will be performed atomically.
>>
>>
>
>would it be much more difficult to allow non-page aligned bufs to be written
>atomically? a fully atomic fs would be very nice. otherwise, a lot of utils
>and shell builtins would have to be modded to insure page alignment. it
>would be neat if all the regular builtins (cp, mv, ln) were atomic. of
>course, even neater would be the ability to group multiple ops into one
>atomic action. (this is probably already planned - it's been a while since i
>read the reiserfs4 paper on the namesys site.)
>
>
>
reiser4 does all this that you ask for, although the user space API is
not yet compiling;-)
--
Hans
next prev parent reply other threads:[~2003-08-29 0:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 17:25 reiser4 data journalling? Tupshin Harper
2003-08-28 17:42 ` Nikita Danilov
2003-08-28 20:48 ` Hans Reiser
2003-08-29 0:18 ` Tom Vier
2003-08-29 0:21 ` Hans Reiser [this message]
2003-08-29 1:23 ` Mike Fedyk
2003-08-29 5:08 ` Oleg Drokin
2003-08-29 17:48 ` Hans Reiser
2003-08-29 18:15 ` Nikita Danilov
2003-08-29 18:17 ` Nikita Danilov
2003-08-29 21:43 ` Hans Reiser
2003-08-29 21:56 ` system_lists
2003-08-30 18:22 ` Andi Kleen
2003-09-02 22:21 ` Hans Reiser
2003-09-03 2:05 ` Tom Vier
2003-08-29 21:47 ` Hans Reiser
2003-08-29 13:12 ` Lars Marowsky-Bree
2003-09-02 22:17 ` Hans Reiser
2003-09-03 10:52 ` Lars Marowsky-Bree
2003-09-03 16:56 ` Hans Reiser
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=3F4E9C6D.2080009@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=tmv@comcast.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.