xfs
[Top] [All Lists]

Re: xfs_fsr, sunit, and swidth

To: Dave Hall <kdhall@xxxxxxxxxxxxxx>
Subject: Re: xfs_fsr, sunit, and swidth
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 17 Apr 2013 02:18:41 +1000
Cc: stan@xxxxxxxxxxxxxxxxx, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <516C649A.8010003@xxxxxxxxxxxxxx>
References: <5143F94C.1020708@xxxxxxxxxxxxxxxxx> <20130316072126.GG6369@dastard> <515082C3.2000006@xxxxxxxxxxxxxx> <515361B5.8050603@xxxxxxxxxxxxxxxxx> <5155F2B2.1010308@xxxxxxxxxxxxxx> <20130331012231.GJ6369@dastard> <515C3BF3.60601@xxxxxxxxxxxxxx> <51684382.50008@xxxxxxxxxxxxxx> <5168AC0B.5010100@xxxxxxxxxxxxxxxxx> <516C649A.8010003@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Apr 15, 2013 at 04:35:38PM -0400, Dave Hall wrote:
> Stan,
> 
> I understand that this will be an ongoing problem.  It seems like
> all I could do at this point would be to ' manually defrag' my
> inodes the hard way by doing this 'copy' operation whenever things
> slow down.  (Either that or go get my PHD in file systems and try to
> come up with a better inode management algorithm.)

No need, I know how to fix it for good. Just add a new btree that
tracks free inodes, rather than having to scan the allocated inode
tree to find free inodes. Shouldn't actually be too difficult to do,
as it's a generic btree and the code to keep both btrees in sync is
a copy of the way the two freespace btrees are kept in sync....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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