|From:||Theodore Tso <tytso-AT-mit.edu>|
|To:||Pavel Machek <pavel-AT-suse.cz>|
|Subject:||Re: [PATCH 0/4] (RESEND) ext3 barrier changes|
|Date:||Wed, 21 May 2008 08:32:55 -0400|
|Cc:||Chris Mason <chris.mason-AT-oracle.com>, Andrew Morton <akpm-AT-linux-foundation.org>, Eric Sandeen <sandeen-AT-redhat.com>, Andi Kleen <andi-AT-firstfloor.org>, linux-ext4-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org, linux-fsdevel-AT-vger.kernel.org|
On Wed, May 21, 2008 at 01:22:25PM +0200, Pavel Machek wrote: > > Ok, Andrew, is this enough to get barrier patch applied and stop > corrupting data in default config, or do you want some more testing? It is for me; I think we have to enable barriers for ext3/4, and then work to improve the overhead in ext4/jbd2. It's probably true that the vast majority of systems don't run under conditions similar to what Chris used to demonstrate the problem, but the default has to be filesystem safety. People who are sure they are extremely unlikely to run into this problem can turn barriers off (and I suspect they won't see that much difference in the most common workloads anyway). - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html
Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds