>Yes, but if you have fragemented free space then it is possible that there
>are not enough free extents large enough (or aligned correctly) to
>allocate more inodes. The number of "free inodes" reported doesn't take
>this into account; it only looks at the number of free blocks and converts
>that to a theoretical number of inodes that could be allocated in that
>space (i.e. it assumes perfect fit and no waste).
>In this "not quite full filesystem" situation, you can write data to the
>filesystem, but any attempt to create a new inode (new file, directory,
>etc) will fail with ENOSPC. This sounds like the symptoms you are
What you described might happen with lot of small files, but in our case,
our attempts fail to create a new inode and fail to write data. You suppose
that we have fractured free spaces, and on these fractures no inodes can be
created. In our case, the situation was different, however as it started to
work again I still can't provide you any xfs_info/debug.
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2989 (20080401) __________
The message was checked by ESET NOD32 Antivirus.