From mboxrd@z Thu Jan 1 00:00:00 1970 From: jim owens Subject: Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2 Date: Tue, 08 Jul 2008 10:03:27 -0400 Message-ID: <487373AF.1030309@hp.com> References: <20080625221835.GQ28100@wotan.suse.de> <1214489061.6237.16.camel@norville.austin.ibm.com> <4863A483.5060303@redhat.com> <1214490465.6237.24.camel@norville.austin.ibm.com> <486C13B7.4030402@hp.com> <20080703111726.GZ29319@disturbed> <486CC446.1050602@hp.com> <0371AF9C-A83A-4584-83D2-6EE9DCEACD77@cam.ac.uk> <4872A044.7070001@hp.com> <20080708015153.GM11558@disturbed> <4873657C.3020601@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Dave Chinner Return-path: Received: from g1t0029.austin.hp.com ([15.216.28.36]:44481 "EHLO g1t0029.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751993AbYGHOEE (ORCPT ); Tue, 8 Jul 2008 10:04:04 -0400 In-Reply-To: <4873657C.3020601@hp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Here is one last point that confuses me so please explain what I have misunderstood: - The XFS bmap api ALWAYS does SYNC, which is why XFS tools are coded that way to expect it. - XFS could implement fiemap the same way to always sync. - And the only use in XFS for NO-SYNC is that Dave might like to sometime see unmodified extent data. Sounds like a good reason to confuse users with the FIEMAP_FLAG_SYNC and make other filesystems do extra work doesn't it? jim