xfs
[Top] [All Lists]

Re: sparse file handling bug in XFS

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: sparse file handling bug in XFS
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 16 Jun 2011 13:57:43 -0400
Cc: Sean Noonan <Sean.Noonan@xxxxxxxxxxxx>, "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>, Martin Bligh <Martin.Bligh@xxxxxxxxxxxx>, Trammell Hudson <Trammell.Hudson@xxxxxxxxxxxx>, Ian Baum <Ian.Baum@xxxxxxxxxxxx>, Stephen Degler <Stephen.Degler@xxxxxxxxxxxx>
In-reply-to: <4DFA3E7D.4030408@xxxxxxxxxxx>
References: <081DDE43F61F3D43929A181B477DCA95639B561F@xxxxxxxxxxxxxxxxxxxx> <4DFA2A76.6000104@xxxxxxxxxxx> <4DFA3E7D.4030408@xxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Jun 16, 2011 at 12:33:49PM -0500, Eric Sandeen wrote:
> Actually this looks like it's a result of
> 
> 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7 xfs: don't truncate prealloc from 
> frequently accessed inodes
> 
> I thought Dave's patch from the "Re: drastic changes to allocsize semantics 
> in or around 2.6.38?"
> thread would fix it, but it doesn't seem to.  Here it is anyway ;)

It should fix the thing about the preallocation staying when removing
and recreating the file.  Keeping pre-allocate blocks around otherwise
is a considered a feature.

<Prev in Thread] Current Thread [Next in Thread>