All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Mirar <mirar-yg@mirar.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>, reiserfs-list@namesys.com
Subject: Re: power loss -> corruption
Date: Thu, 08 May 2003 22:58:35 +0400	[thread overview]
Message-ID: <3EBAA8DB.3080202@namesys.com> (raw)
In-Reply-To: <m17k911sq4.fsf@orchid.mirar.org>

You have run into the disadvantage of meta-data journaling, which is 
that files that you are writing to may be corrupted if you crash.  This 
disadvantage exists for performance reasons: using traditional 
journaling approaches such as V3 uses, if you journal the data you must 
write it twice.  V3 also offers you the option of performing ordered 
writes, in which, if I remember right, metadata is only updated after 
the data reaches disk.

V4 uses a completely different technology we call wandering logs, in 
which every filesystem operation is performed as a fully atomic 
transaction, and because of its new design, there is very little 
performance cost (in fact, reiser4 is higher performance than V3).  We 
hope V4 will be ready for prime time sometime this summer.

-- 
Hans



  parent reply	other threads:[~2003-05-08 18:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  5:15 How to work around bad blocks? Dirk Leber
2003-03-10 20:50 ` Anders Widman
2003-05-08 11:18 ` power loss -> corruption Mirar
2003-05-08 11:48   ` Dieter Nützel
2003-05-08 12:06     ` Mirar
2003-05-08 13:02       ` Dieter Nützel
2003-05-08 13:19         ` Mirar
2003-05-08 13:31           ` Dieter Nützel
2003-05-15  8:40             ` Mirar
2003-05-15 11:23               ` Dieter Nützel
2003-05-15 15:17                 ` Mirar
2003-05-08 18:58           ` Hans Reiser [this message]
2003-05-08 19:20             ` Mirar
2003-05-08 19:28               ` Hans Reiser
2003-05-08 19:31               ` Hans Reiser
2003-05-08 19:39                 ` Mirar
2003-05-08 12:02   ` Bill Rees
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 12:23 berthiaume_wayne
2003-05-08 12:32 ` Mirar
2003-05-08 12:38   ` Marc-Christian Petersen
2003-05-08 12:34 ` Anders Widman
2003-05-08 12:39   ` Marc-Christian Petersen
2003-05-08 13:01     ` Dieter Nützel
2003-05-08 13:24     ` Chris Mason
2003-05-08 13:36       ` Dieter Nützel
2003-05-08 13:40         ` Chris Mason
2003-05-08 12:39   ` Dieter Nützel
2003-05-08 19:37 Fong Vang
2003-05-08 19:52 ` Hans Reiser
2003-05-15 22:38 Anders Widman

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=3EBAA8DB.3080202@namesys.com \
    --to=reiser@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=mirar-yg@mirar.org \
    --cc=reiserfs-list@namesys.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.