From: "Stephen C. Tweedie" <sct@redhat.com>
To: Hans Reiser <reiser@namesys.com>
Cc: foner-reiserfs@media.mit.edu, linux-kernel@vger.kernel.org,
Stephen Tweedie <sct@redhat.com>
Subject: Re: ReiserFS data corruption in very simple configuration
Date: Wed, 3 Oct 2001 17:17:03 +0100 [thread overview]
Message-ID: <20011003171703.B5209@redhat.com> (raw)
In-Reply-To: <200109221000.GAA11263@out-of-band.media.mit.edu> <3BB88B63.AEE6EF8E@namesys.com>
In-Reply-To: <3BB88B63.AEE6EF8E@namesys.com>; from reiser@namesys.com on Mon, Oct 01, 2001 at 07:27:31PM +0400
Hi,
On Mon, Oct 01, 2001 at 07:27:31PM +0400, Hans Reiser wrote:
> This is the meaning of metadata journaling: that writes in progress at the time
> of the crash may write garbage, but you won't need to fsck. You can get this
> behaviour with other filesystems like FFS also. If you cannot accept those
> terms of service, you might use ext3 with data journaling on, but then your
> performance will be far worse.
ext3 with ordered data writes has performance nearly up to the level
of the fast-and-loose writeback mode for most workloads, and still
avoids ever exposing stale disk blocks after a crash.
Sure, it's a tradeoff, but there are positions between the two
extremes (totally unordered data writes, and totally journaled data
writes) which offer a good compromise here.
Cheers,
Stephen
next prev parent reply other threads:[~2001-10-03 16:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 10:00 ReiserFS data corruption in very simple configuration foner-reiserfs
2001-09-22 12:47 ` Nikita Danilov
2001-09-22 20:44 ` foner-reiserfs
2001-09-25 13:28 ` Stephen C. Tweedie
2001-09-29 4:44 ` Lenny Foner
2001-09-29 12:52 ` [reiserfs-list] " Lehmann
2001-10-01 1:00 ` foner-reiserfs
2001-10-01 1:26 ` Lehmann
2001-10-01 2:32 ` foner-reiserfs
2001-10-03 16:28 ` Toby Dickenson
2001-10-01 11:30 ` Stephen C. Tweedie
2001-09-24 9:25 ` [reiserfs-list] " Jens Benecke
2001-10-14 14:52 ` Chris Mason
2001-10-14 18:19 ` Jens Benecke
2001-10-14 20:04 ` Hans Reiser
2001-10-14 23:32 ` Bernd Eckenfels
2001-09-25 20:13 ` Mike Fedyk
2001-09-26 14:43 ` Stephen C. Tweedie
2001-10-01 3:38 ` Mike Fedyk
2001-10-03 16:14 ` Stephen C. Tweedie
2001-10-01 15:27 ` Hans Reiser
2001-10-03 16:17 ` Stephen C. Tweedie [this message]
2001-10-03 20:06 ` Pascal Schmidt
2001-10-04 11:02 ` Stephen C. Tweedie
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=20011003171703.B5209@redhat.com \
--to=sct@redhat.com \
--cc=foner-reiserfs@media.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox