imaxpct sets how much filesystem space can be consumed by the inodes
themselves. It is not reserved, just an upper bound.
You would want to raise the imaxpct, if anything, to test this.
However, if you were able to lower it, that means that you had not yet
hit the old max, so that's not the problem.
Still thinking...
-Eric
On Wed, 2002-05-01 at 13:23, bren@xxxxxxxxxxxxx wrote:
> So 25% of the drive is reserved for inodes. There is roughly 25% free space
> reported. Is the space that is reported as being free actually reserved? I
> tried
> lowering the imaxpct, with no change.
>
> Quoting Eric Sandeen <sandeen@xxxxxxx>:
>
> > Just for kicks you could try using xfs_growfs to bump the inode maxpct a
> > bit, although from df -i I don't think that's the problem...
> >
> > -Eric
> >
> > On Wed, 2002-05-01 at 12:23, bren@xxxxxxxxxxxxx wrote:
> > > Ok. I've upgraded to 2.4.18 with XFS 1.1. Same results...
> >
> > --
> > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
> > sandeen@xxxxxxx SGI, Inc.
> >
> >
>
>
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|