Re: Free space question

[Steve Lord <lord@sgi.com>]

On Wed, 2002-05-01 at 13:50, bren@sio.midco.net wrote:
> Odd...I get this a bunch of times:
> 
> can't seek in filesystem at bb 8861651024
> can't read btree block 7/1107492864
> can't seek in filesystem at bb 17048932432
> can't read btree block 7/2130903040
> 
> when I do a freesp with xfs_db. I've checked this fs with xfs_repair more than
> once...


Ugh, try xfs_check on the unmounted device, it will look at different
things. Those numbers look way out of bounds.

Steve

> 
> Quoting Steve Lord <lord@sgi.com>:
> 
> > On Wed, 2002-05-01 at 13:26, Eric Sandeen wrote:
> > > 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
> > > 
> > 
> > 
> > Try running xfs_db -r /dev/xxx
> > 
> > then run the freesp command, this will report how freespace is
> > distributed on the filesystem. quit gets you out of xfs_db.
> > 
> > Steve
> > 
> > -- 
> > 
> > Steve Lord                                      voice: +1-651-683-3511
> > Principal Engineer, Filesystem Software         email: lord@sgi.com
> > 
> > 
> 
> 
-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@sgi.com