From: Mark Lord Subject: Re: ext4 ioctl(FIEMAP) bug? observed in 2.6.29.4 (32-bit x86) Date: Mon, 03 Aug 2009 10:50:41 -0400 Message-ID: <4A76F941.5060006@rtr.ca> References: <4A76069C.1010801@rtr.ca> <20090803074554.GA21042@skywalker> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux Kernel , linux-ext4@vger.kernel.org, sandeen@redhat.com To: "Aneesh Kumar K.V" Return-path: Received: from rtr.ca ([76.10.145.34]:40055 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932157AbZHCOul (ORCPT ); Mon, 3 Aug 2009 10:50:41 -0400 In-Reply-To: <20090803074554.GA21042@skywalker> Sender: linux-ext4-owner@vger.kernel.org List-ID: Aneesh Kumar K.V wrote: > On Sun, Aug 02, 2009 at 05:35:24PM -0400, Mark Lord wrote: .. >> 2.6.29.4: >> The output below shows the sequence of FIEMAP calls >> on the single massive file. Notice that the first call >> returned the "LAST" flag set, despite there being many >> many more extents after that bunch. >> > > Can you try with > > commit c9877b205f6ce7943bb95281342f4001cc1c00ec > Author: Eric Sandeen > Date: Fri May 1 23:32:06 2009 -0400 > > ext4: fix for fiemap last-block test .. Ahh.. good to see it already upstream, thanks. I cannot easily reproduce the bug, so no re-test here. And my app (hdparm) simply now ignores the LAST flag as a workaround. Thanks