Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932631AbWEXHQi (ORCPT ); Wed, 24 May 2006 03:16:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932633AbWEXHQi (ORCPT ); Wed, 24 May 2006 03:16:38 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:9379 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S932631AbWEXHQi (ORCPT ); Wed, 24 May 2006 03:16:38 -0400 Date: Wed, 24 May 2006 00:16:00 -0700 From: Jeremy Higdon To: Nathan Scott Cc: Jan Engelhardt , xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: XFS write speed drop Message-ID: <20060524071600.GF586512@sgi.com> References: <20060522105326.A212600@wobbly.melbourne.sgi.com> <20060523084309.A239136@wobbly.melbourne.sgi.com> <20060524082218.A267844@wobbly.melbourne.sgi.com> <20060524091741.D267844@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060524091741.D267844@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1544 Lines: 33 On Wed, May 24, 2006 at 09:17:41AM +1000, Nathan Scott wrote: > On Wed, May 24, 2006 at 08:22:19AM +1000, Nathan Scott wrote: > > > > Not sure what you're trying to say here. Yes, barriers are on > > by default now if the hardware supports them, yes, they will > > slow things down relative to write-cache-without-barriers, and > > yes we all knew that ... its not the case that someone "did not > > notice" or forgot about something. There is no doubt that this > > is the right thing to be doing by default - there's no way that > > I can tell from inside XFS in the kernel that you have a UPS. ;) > > Oh, I realised I've slightly misread your mail, you said... > > | I do not actually need barriers (or an UPS, to poke on another thread), > | because power failures are rather rare in Germany. > > Hmm, even harder for us to detect at runtime, in the kernel, > that you're in Germany. :) > > Power failures aren't the only thing to cause crashes, however. There have been several examples of filesystem corruption without power failures too, though that is a common cause. It can even happen on a normal system shutdown if there is no synchronize operation to the disk at shutdown time, depending on how much data is in the cache and how long you have until the ATA chip is reset. jeremy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/