From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hans Reiser <reiser@namesys.com>
Subject: Re: [PATCH 0/2] enable write barriers by default
Date: Fri, 04 Aug 2006 21:39:39 -0600
Message-ID: <44D412FB.8080902@namesys.com>
References: <20060804135140.GA942@watt.suse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org, akpm@osdl.org,
	reiserfs-dev@namesys.com, Martin Steigerwald <Martin@lichtvoll.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from thebsh.namesys.com ([212.16.7.65]:41123 "HELO
	thebsh.namesys.com") by vger.kernel.org with SMTP id S932483AbWHEEjn
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Sat, 5 Aug 2006 00:39:43 -0400
To: Chris Mason <mason@suse.com>
In-Reply-To: <20060804135140.GA942@watt.suse.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Chris Mason wrote:

>Hello everyone,
>
>ReiserFS and ext3 have had code to support forcing cache flushes for a
>while, but it has been off by default.
>
>These two patches enable it by default on both filesystems.  Disabling
>barriers can be done with:
>
>mount -o barrier=none in reiser
>mount -o barrier=0 in ext3
>
>-chris
>
>
>
>  
>
Please explain when cache flushes occur now.  For every fsync on a drive
that does not support write barriers?  Which drives support it?

Did this only get enabled now because it is only now that someone from
the press is paying attention to it?

This is the price we paid for losing Andre, yes?