| To: | Chris Wedgwood <cw@xxxxxxxx> |
|---|---|
| Subject: | Re: Allocating inodes from a single block |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 17 Jul 2007 20:43:17 -0500 |
| Cc: | Michael Nishimoto <miken@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20070717201921.GA26309@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <469D0666.6040908@xxxxxxxxx> <20070717201921.GA26309@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.4 (Macintosh/20070604) |
Chris Wedgwood wrote: > On Tue, Jul 17, 2007 at 11:11:50AM -0700, Michael Nishimoto wrote: > >> Filesystem free space becomes fragmented over time. It's possible >> for total free space to be a decent size and still not have a chunk >> large enough to allocate new inodes. > > by default there is a restriction that indoes shouldn't consume more > that 25% of the total space > > see the mkfs.xfs man-page for details, search for 'maxpct' > > for existing filesystems you can use xfs_db to rewrite this value The problem is that inodes are allocated in "clusters" of blocks. If your free blocks aren't such that they can form a cluster, I think you're out of luck when trying to allocate new inodes if your existing clusters are full. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Advocacy] Re: 3ware 9650 tips, David Chinner |
|---|---|
| Next by Date: | Re: Allocating inodes from a single block, Nathan Scott |
| Previous by Thread: | Re: Allocating inodes from a single block, Michael Nishimoto |
| Next by Thread: | Re: Allocating inodes from a single block, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |