From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2
Date: Thu, 26 Jun 2008 14:27:31 +0100
Message-ID: <20080626132731.GB3356@shareable.org>
References: <20080625221835.GQ28100@wotan.suse.de> <20080626093634.GA30025@shareable.org> <20080626102403.GN6239@webber.adilger.int> <20080626121950.GB32417@shareable.org> <20080626131600.GS29319@disturbed>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Andreas Dilger <adilger@sun.com>, Mark Fasheh <mfasheh@suse.com>,
	linux-fsdevel@vger.kernel.org, Andreas Dilger <adilger@shaw.ca>,
	Kalpak Shah <Kalpak.Shah@sun.com>,
	Eric Sandeen <san
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail2.shareable.org ([80.68.89.115]:53017 "EHLO
	mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1763916AbYFZN1d (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 26 Jun 2008 09:27:33 -0400
Content-Disposition: inline
In-Reply-To: <20080626131600.GS29319@disturbed>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Dave Chinner wrote:
> > It's not harmful but suggests it might do something important -
> > e.g. provide atomicity between the fsync and getting extends.
> 
> It does precisely that.

Ok - so nobody can modify the file in between?  Is that useful, given
the file can be modified as soon as FIEMAP returns anyway?  I suppose
it does ensure all the instantiated data blocks will be allocated on
disk in the returned extents.

-- Jamie