From: Jeff Garzik Subject: Re: Proposal for "proper" durable fsync() and fdatasync() Date: Tue, 26 Feb 2008 11:43:45 -0500 Message-ID: <47C441C1.5060305@garzik.org> References: <20080226072649.GB30238@shareable.org> <20080225234319.f4589ae4.akpm@linux-foundation.org> <20080226075921.GG30238@shareable.org> <200802262016.11297.nickpiggin@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jamie Lokier , Andrew Morton , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Chris Wedgwood To: Nick Piggin Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:49186 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753509AbYBZQnx (ORCPT ); Tue, 26 Feb 2008 11:43:53 -0500 In-Reply-To: <200802262016.11297.nickpiggin@yahoo.com.au> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Nick Piggin wrote: > Anyway, the idea of making fsync/fdatasync etc. safe by default is > a good idea IMO, and is a bad bug that we don't do that :( Agreed... it's also disappointing that [unless I'm mistaken] you have to hack each filesystem to support barriers. It seems far easier to make sync_blkdev() Do The Right Thing, and magically make all filesystems data-safe. Jeff