From: Andrew Morton <akpm@osdl.org>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: precise characterization of ext3 atomicity
Date: Thu, 4 Sep 2003 09:12:56 -0700 [thread overview]
Message-ID: <20030904091256.1dca14a5.akpm@osdl.org> (raw)
In-Reply-To: <3F576176.3010202@namesys.com>
Hans Reiser <reiser@namesys.com> wrote:
>
> Perhaps the following is correct?
>
> By contrast, ext3 in data=journal and data=ordered modes only guarantees the atomicity of a single write
> that does not span a page boundary, and it guarantees that its internal
> metadata will not be corrupted even if your application's data is
> corrupted after the crash (due to the application spreading what should be committed atomically across more than one block).
Correct != comprehensible ;)
"In all journalling modes ext3 guarantees metadata consistency after a
crash. In its data=journal and data=ordered modes ext3 also guarantees that
user data is consistent with metadata after a crash.
However ext3 does not provide user data atomicity guarantees beyond the
scope of a single filesystem disk block (usually 4 kilobytes). If a
single write() spans two disk blocks it is possible that a crash partway
through the write will result in only one of those blocks appearing in the
file after recovery"
next prev parent reply other threads:[~2003-09-04 16:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 14:20 Hans Reiser
2003-09-04 15:55 ` Andrew Morton
2003-09-04 15:59 ` Hans Reiser
2003-09-04 16:12 ` Andrew Morton [this message]
2003-09-04 16:25 ` Hans Reiser
2003-09-04 18:15 ` Mike Fedyk
2003-09-04 16:05 ` Antonio Vargas
2003-09-04 18:37 ` Hans Reiser
2003-09-04 19:12 ` Mike Fedyk
2003-09-04 21:03 ` Hans Reiser
2003-09-04 19:28 ` Andreas Dilger
2003-09-04 21:32 ` Hans Reiser
2003-09-04 22:03 ` Andreas Dilger
2003-09-05 13:47 ` Chris Mason
2003-09-09 13:09 ` Pavel Machek
2003-09-09 19:21 ` Gábor Lénárt
2003-09-09 19:43 ` Mike Fedyk
2003-09-04 20:16 ` Daniel Phillips
2003-09-04 20:10 ` Andrew Morton
2003-09-04 21:08 ` Daniel Phillips
2003-09-04 21:39 ` Hans Reiser
2003-09-04 21:59 ` Daniel Phillips
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=20030904091256.1dca14a5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome