Re: [PATCH 0/4] (RESEND) ext3 barrier changes
From: Pavel Machek
Date: Mon May 19 2008 - 05:03:30 EST
On Fri 2008-05-16 13:05:45, Andrew Morton wrote:
> On Fri, 16 May 2008 14:02:46 -0500 Eric Sandeen <sandeen@xxxxxxxxxx> wrote:
> > A collection of patches to make ext3 & 4 use barriers by
> > default, and to call blkdev_issue_flush on fsync if they
> > are enabled.
> Last time this came up lots of workloads slowed down by 30% so I
> dropped the patches in horror.
> I just don't think we can quietly go and slow everyone's machines down
> by this much. The overhead of journalling is already pretty horrid.
> If we were seeing a significant number of "hey, my disk got wrecked"
> reports which attributable to this then yes, perhaps we should change
> the default. But I've never seen _any_, although I've seen claims that
> others have seen reports.
Do you remember seeing "my disk was wrecked" for reiserfs?
I believe I got some corruption, but it was
a) long time ago
b) took half a year of hard powerdowns to provoke
c) I did not report it anywhere because ... it just was not
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/