All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Tupshin Harper <tupshin@tupshin.com>,
	Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: reiser4 data journalling?
Date: Fri, 29 Aug 2003 00:48:36 +0400	[thread overview]
Message-ID: <3F4E6AA4.3030900@namesys.com> (raw)
In-Reply-To: <16206.16138.72832.920045@laputa.namesys.com>

Nikita Danilov wrote:

>Tupshin Harper writes:
> > Will reiser4 have options equivalent to ext3's data=journal and 
> > data=ordered options? My understanding is that reiser4(and reiser3) do 
> > the equivalent of ext3's writeback mode(correct?). Any plans for the 
>
>reiserfs has meta-data only journalling by default (equivalent to
>writeback mode), and optionally supports full data journalling (Chris
>patches).
>
>reiser4 supports full data journalling only
>
full data journaling means that if you perform writes that are 4k or 
less, and page align them, they will be performed atomically. 

Reiser4 is a fully atomic filesystem, and that means that you can 
perform a set of filesystem operations of any size, and they will be 
performed atomically.  By default, every fs system call is performed 
atomically.

Please describe reiser4 as an atomic filesystem, not as (just) a data 
journaling filesystem, ok?

>, but it is still faster than
>ext3-writeback.
>
>Look at http://www.namesys.com/benchmarks.html for last benchmarking
>results.
>
> > other modes in order to maximize data integrity?
> > 
> > -Tupshin
> > 
>
>Nikita.
>
>
>  
>


-- 
Hans



  reply	other threads:[~2003-08-28 20:48 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 [this message]
2003-08-29  0:18     ` Tom Vier
2003-08-29  0:21       ` Hans Reiser
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=3F4E6AA4.3030900@namesys.com \
    --to=reiser@namesys.com \
    --cc=Nikita@Namesys.COM \
    --cc=reiserfs-list@namesys.com \
    --cc=tupshin@tupshin.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 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.