xfs
[Top] [All Lists]

Re: XFS holding onto disk memory

To: Steve Lord <lord@xxxxxxx>
Subject: Re: XFS holding onto disk memory
From: Walt H <waltabbyh@xxxxxxxxxxx>
Date: Wed, 26 Mar 2003 18:06:29 -0800
Cc: Mark Grimes <MGrimes@xxxxxxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1048706978.23087.83.camel@xxxxxxxxxxxxxxxxxxxx>
References: <057889C7F1E5D61193620002A537E8690AD0AA@NCBDC> <1048706978.23087.83.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030326
Steve Lord wrote:
On Wed, 2003-03-26 at 13:26, Mark Grimes wrote:

Is this a patch I can try?
I can build with XFS v1.2 if necessary.


Not yet, it only worked for the first time a few days ago, and
that was on Irix.

Steve


I'm not tremendously familiar with the innards of a filesystem, so this question may be totally off the mark. But.... Would freeing of inodes allow the system to have contiguous free space? I've found when testing servers prior to production, that if I create thousands of files and potentially many runs of bonnie++ etc.. that certain aspects of filesystem operation are slowed down, even after removing all the test files. For example, if after removing all these test files and I want/need to run an xfs_check/xfs_repair on said filesystem, it can drag on for quite some time. This happens on a filesystem which now has very little on it. Would freeing inodes help something such as this?

-Walt



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