Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753909Ab0LFRDe (ORCPT ); Mon, 6 Dec 2010 12:03:34 -0500 Received: from xenotime.net ([72.52.115.56]:38727 "HELO xenotime.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752989Ab0LFRDd (ORCPT ); Mon, 6 Dec 2010 12:03:33 -0500 Date: Mon, 6 Dec 2010 09:03:23 -0800 From: Randy Dunlap To: Olaf van der Spek Cc: linux-kernel@vger.kernel.org Subject: Re: Atomic non-durable file write API Message-Id: <20101206090323.6b049846.rdunlap@xenotime.net> In-Reply-To: References: Organization: YPO4 X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1150 Lines: 30 On Mon, 6 Dec 2010 17:45:23 +0100 Olaf van der Spek wrote: > On Mon, Nov 29, 2010 at 1:37 PM, Olaf van der Spek wrote: > > Hi, > > > > Since the introduction of ext4, some apps/users have had issues with > > file corruption after a system crash. It's not a bug in the FS AFAIK > > and it's not exclusive to ext4. > > Writing a temp file, fsync, rename is often proposed. However, the > > durable aspect of fsync isn't always required and this way has other > > issues. > > What is the recommended way for atomic non-durable (complete) file writes? > > > > I'm also wondering why FSs commit after open/truncate but before > > write/close. AFAIK this isn't necessary and thus suboptimal. > > Somebody? > -- maybe try linux-fsdevel@vger.kernel.org or linux-ext4@vger.kernel.org mailing lists? --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- 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/