From: =?ISO-8859-1?Q?P=E1draig_Brady?= Subject: Re: Files full of zeros with coreutils-8.11 and xfs (FIEMAP related?) Date: Thu, 14 Apr 2011 15:59:31 +0100 Message-ID: <4DA70BD3.1070409@draigBrady.com> References: <20110414102608.GA1678@x4.trippels.de> <20110414120635.GB1678@x4.trippels.de> <20110414140222.GB1679@x4.trippels.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: coreutils-mXXj517/zsQ@public.gmane.org, Markus Trippelsdorf To: xfs-oss , linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: In-Reply-To: <20110414140222.GB1679-tLCgZGx+iJ+kxVt8IV0GqQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: coreutils-bounces+gcgcg-coreutils=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: coreutils-bounces+gcgcg-coreutils=m.gmane.org-mXXj517/zsQ@public.gmane.org List-Id: linux-ext4.vger.kernel.org On 14/04/11 15:02, Markus Trippelsdorf wrote: >>> Hi P?draig, >>> >>> here you go: >>> + filefrag -v unwritten.withdata >>> Filesystem type is: ef53 >>> File size of unwritten.withdata is 5120 (2 blocks, blocksize 4096) >>> ext logical physical expected length flags >>> 0 0 274432 2560 unwritten,eof >>> unwritten.withdata: 1 extent found >>> >>> Please notice that this also happens with ext4 on the same kernel. >>> Btrfs is fine. >> > `filefrag -vs` fixes the issue on both xfs and ext4. So in summary, currently on (2.6.39-rc3), the following will (usually?) report a single unwritten extent, on both ext4 and xfs fallocate -l 10MiB -n k dd count=10 if=/dev/urandom conv=notrunc iflag=fullblock of=k filefrag -v k # grep for an extent without unwritten || fail This particular issue has been discussed so far at: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8411 Note there it was stated there that ext4 had this fixed as of 2.6.39-rc1, so maybe there is something lurking? cheers, P?draig.