| To: | Mark Grimes <MGrimes@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS holding onto disk memory |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Wed, 26 Mar 2003 13:16:32 -0600 (CST) |
| Cc: | "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <057889C7F1E5D61193620002A537E8690AD0A9@NCBDC> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | XFS holding onto disk memory, Mark Grimes |
|---|---|
| Next by Date: | [Bug 230] umount hangs after high disk load, bugzilla-daemon |
| Previous by Thread: | XFS holding onto disk memory, Mark Grimes |
| Next by Thread: | Re: XFS holding onto disk memory, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |