From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Harald Arnesen <skogtun.harald@gmail.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
tytso@mit.edu
Subject: Re: [ext4] Documentation patch
Date: Mon, 01 Dec 2008 11:58:52 -0600 [thread overview]
Message-ID: <493425DC.1010008@redhat.com> (raw)
In-Reply-To: <20081201165700.GA26680@infradead.org>
Christoph Hellwig wrote:
> On Mon, Dec 01, 2008 at 05:46:56PM +0100, Harald Arnesen wrote:
>> So when comparing with a metadata-only journalling filesystem, such
>> - as ext3, use `mount -o data=writeback'. And you might as well use
>> + as jfs or xfs, use `mount -o data=writeback'. And you might as well use
>
> data=ordered comes closest to what xfs does for quite a long time..
Agreed; that whole bit which mentions other filesystem comparisons
should probably be stricken, unless it can be
proven/demonstrated/substantiated that ext3 really does "offer higher
data integrity guarantees than most" at this point.
data=ordered ensures that stale data won't be exposed on a crash; xfs
won't do this (it'd be a security bug) and I'd be surprised if jfs or
reiserfs do either. And it probably *should* be mentioned that
data=writeback bears this risk.
And until ext3 turns on barriers by default, I don't think it's fair to
talk too much about integrity guarantees. :)
-Eric
next prev parent reply other threads:[~2008-12-01 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 16:46 [ext4] Documentation patch Harald Arnesen
2008-12-01 16:57 ` Christoph Hellwig
2008-12-01 17:58 ` Eric Sandeen [this message]
2008-12-01 20:58 ` Theodore Tso
2008-12-06 22:25 ` Theodore Tso
2008-12-06 23:33 ` Eric Sandeen
2008-12-06 23:33 ` Eric Sandeen
2008-12-07 18:39 ` Theodore Tso
2008-12-07 20:43 ` Eric Sandeen
2008-12-07 20:43 ` Eric Sandeen
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=493425DC.1010008@redhat.com \
--to=sandeen@redhat.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skogtun.harald@gmail.com \
--cc=tytso@mit.edu \
/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.