| To: | Eric Sandeen <sandeen@xxxxxxx> |
|---|---|
| Subject: | Re: XFS holding onto disk memory |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 26 Mar 2003 13:23:59 -0600 |
| Cc: | Mark Grimes <MGrimes@xxxxxxxxxxxxxxxxx>, "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.44.0303261314300.7210-100000@xxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | |
| References: | <Pine.LNX.4.44.0303261314300.7210-100000@xxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Wed, 2003-03-26 at 13:16, Eric Sandeen wrote: > > Is this expected behavior? Is there a way to recover the on disk memory > > without unmounting the filesystem? > > XFS dynamically allocates inodes as they are requested, but they are > never freed. Even unmounting won't get this back for you. > > So if you fill your disk with 0-length files, the space allocated > for inodes will always & forever be allocated for those inodes. > > (compare this to ext2, where inode space is permanently allocated > at mkfs time). > > You can use xfs_growfs to change the % of the disk which can be used > for inodes, though. > > -Eric And we do have freeing of inodes working in house. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 230] umount hangs after high disk load, bugzilla-daemon |
|---|---|
| Next by Date: | RE: XFS holding onto disk memory, Mark Grimes |
| Previous by Thread: | Re: XFS holding onto disk memory, Eric Sandeen |
| Next by Thread: | RE: XFS holding onto disk memory, Mark Grimes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |