From: Pavel Machek Subject: Re: [PATCH 1/4] ext3: enable barriers by default Date: Mon, 19 May 2008 10:58:42 +0200 Message-ID: <20080519085842.GA2013@elf.ucw.cz> References: <482DDA56.6000301@redhat.com> <482DDB13.1050708@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ext4 development , linux-kernel Mailing List , linux-fsdevel , Andrew Morton , Jamie Lokier To: Eric Sandeen Return-path: Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:57273 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751433AbYESI5o (ORCPT ); Mon, 19 May 2008 04:57:44 -0400 Content-Disposition: inline In-Reply-To: <482DDB13.1050708@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Fri 2008-05-16 14:05:55, Eric Sandeen wrote: > I can't think of any valid reason for ext3 to not use barriers when > they are available; I believe this is necessary for filesystem > integrity in the face of a volatile write cache on storage. > > An administrator who trusts that the cache is sufficiently battery- > backed (and power supplies are sufficiently redundant, etc...) > can always turn it back off again. > > SuSE has carried such a patch for quite some time now. > > Also document the mount option while we're at it. > > Signed-off-by: Eric Sandeen > Acked-by: Jan Kara Yes please. Safe defaults are the way to go. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html