From: Chris Mason <chris.mason@oracle.com>
To: jack@suse.cz, tytso@mit.edu, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH RFC] Ext3 data=guarded
Date: Tue, 8 Sep 2009 11:09:53 -0400 [thread overview]
Message-ID: <1252422595-4554-1-git-send-email-chris.mason@oracle.com> (raw)
Hello everyone,
Here is a respin of the ext3 data=guarded code. This adds a new mount option
(mount -o data=guarded) to prevent garbage in files after a crash.
The main difference from data=ordered is that data=guarded only updates
the on disk i_size after all of the data blocks are on disk. This allows
us to avoid flushing all the data pages down to disk with every commit.
More details are in the patch emails. It has survived some long stress tests,
but I do still need to hammer on O_DIRECT and hole filling.
Jan Kara has already picked up patch 1/2, but I'm including it here in case
anyone wants to test the code.
One important part of this patch series is that it tries to have minimal
impact on the other data modes of ext3. So, data=ordered and data=writeback
should stay the same in performance and reliability with this code.
-chris
next reply other threads:[~2009-09-08 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 15:09 Chris Mason [this message]
2009-09-08 15:09 ` [PATCH 1/2] Ext3: Fix race in ext3_mark_inode_dirty Chris Mason
2009-09-08 15:09 ` [PATCH 2/2] Ext3: data=guarded mode Chris Mason
2009-09-15 17:29 ` Jan Kara
2009-09-15 18:39 ` Chris Mason
2009-09-16 14:09 ` Jan Kara
2009-09-16 14:37 ` Chris Mason
2009-09-21 16:29 ` Chris Mason
2009-09-24 16:16 ` Chris Mason
2009-09-17 21:53 ` [PATCH RFC] Ext3 data=guarded Jamie Lokier
2009-09-17 22:19 ` Chris Mason
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=1252422595-4554-1-git-send-email-chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).