|| ||Chris Mason <email@example.com> |
|| ||firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
|| ||[PATCH RFC] Ext3 data=guarded |
|| ||Tue, 8 Sep 2009 11:09:53 -0400|
|| ||Article, Thread
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/