[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090326024220.GB27004@srcf.ucam.org>
Date: Thu, 26 Mar 2009 02:42:20 +0000
From: Matthew Garrett <mjg@...hat.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Theodore Tso <tytso@....edu>,
Christoph Hellwig <hch@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Arjan van de Ven <arjan@...radead.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Nick Piggin <npiggin@...e.de>,
Jens Axboe <jens.axboe@...cle.com>,
David Rees <drees76@...il.com>, Jesper Krogh <jesper@...gh.cc>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.29
On Wed, Mar 25, 2009 at 10:36:31PM -0400, Jeff Garzik wrote:
> Matthew Garrett wrote:
> >The problem is that you're insisting that the only way
> >applications can ensure that their requests occur in order is to use
> >fsync(), which will achieve that but also provides guarantees above and
> >beyond what the majority of applications want.
>
> That remains a true statement... without the *sync* syscalls, you
> still do not have a _guarantee_ writes occur in a certain order.
The interesting case is whether data hits disk before metadata when
renaming over the top of an existing file, which appears to be
guaranteed in the default ext4 configuration now? I'm sure there are
filesystems where this isn't the case, but that's mostly just an
argument that it's not sensible to use those filesystems if your
system's at any risk of crashing.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists