On Wed, May 01, 2002 at 12:23:59PM -0500, bren@xxxxxxxxxxxxx wrote:
> Ok. I've upgraded to 2.4.18 with XFS 1.1. Same results...
> df -i reports:
> 952000 117248 834752 12% /mnt
> df -h:
> 948M 745M 204M 79% /mnt
> Yet simply touching a new file returns:
> touch: file: No space left on device
This is quite a common problem with XFS filesystems in academic
fileserver applications. What's probably going on here is that
you have enough fragmentation that XFS cannot find a 64K extent to
allocate for inodes. Back when it wasn't safe to use xfs_fsr on
Irix (it had a nasty habit of eating files with lseek holes, among
other ugliness) we used to have to regularly dump, recreate, and
restore the student home directories at the university where I
worked, in order to get around this.
Have a look at xfs_db -c freesp and see if you've got any extents
64K or larger left free. If you don't, you won't be able to create
files once you've used up all the inodes in the extents already thus
allocated. However, if you can find a little bit of stuff to delete
so fsr can do its thing, it will probably solve your problem for you.