From: Mark Fasheh Subject: Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2 Date: Wed, 2 Jul 2008 14:20:47 -0700 Message-ID: <20080702212047.GL28100@wotan.suse.de> References: <20080625221835.GQ28100@wotan.suse.de> <4863A1C5.7020403@redhat.com> <20080627014119.GW29319@disturbed> <20080627094156.GA30200@shareable.org> <20080627224843.GZ6239@webber.adilger.int> <4865BC50.2030804@redhat.com> <20080702062612.GP6239@webber.adilger.int> <20080702142854.GB2993@shareable.org> Reply-To: Mark Fasheh Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andreas Dilger , Eric Sandeen , linux-fsdevel@vger.kernel.org, Andreas Dilger , Kalpak Shah , Josef Bacik To: Jamie Lokier Return-path: Received: from ns.suse.de ([195.135.220.2]:56882 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760303AbYGBVUt (ORCPT ); Wed, 2 Jul 2008 17:20:49 -0400 Content-Disposition: inline In-Reply-To: <20080702142854.GB2993@shareable.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Jul 02, 2008 at 03:28:54PM +0100, Jamie Lokier wrote: > Ok, wouldn't be appropriate to include the extent of the index block > as well, somewhere, so that userspace can see which parts of the disk > must be read to read the file? Mapping meta data doesn't belong in fiemap - we can come up with a dedicated interface for that at a future date. --Mark -- Mark Fasheh