I got only 4 responses, according to Birger Wathne ,
vxfs is extent based, so it shouldn't run out of inodes unless you have an
extreme number of files.
Your problem could be that your free space is located in small extents
spread throughout the file system-
I saw something somewhere that to go beyond a certain number of files in a
vxfs file system you had to turn on the largefiles option. I don't
remember the limit.
Perhaps you should try defragmenting your file system? Check your
df -o s
will list your free extents of different sizes.
/usr/lib/fs/vxfs/fsadm -E <mount point> will report on fragmentation
fsadm -e will defragment. Read 'man fsadm_vxfs'
IN FACT, I tried the command /usr/lib/fs/vxfs/fsadm -e /m6 before I write to
the mailing list. But It seems that the command doesnt solve my problem,
althought it can defragment the file system. I really dont know what the
Others have the following idea,
u need to re-construct the filesystem
using mkfs -i u can increase the inods.
my original question:
On Wed, 21 Jun 2000, zhouna wrote:
> I got the following messages on a box which is runing sun solaris 2.6,
> veritas file system and veritas volumn manager.
> un 21 16:48:22 abc.test.com unix: msgcnt 3702 vxfs: mesg 011: vx_noinode -
> /m6 file system out of inodes
> $ df -k /m6
> Filesystem kbytes used avail capacity Mounted on
> 195019776 174719432 20141752 90% /m6
> I was wondering if there is a way to increase the inodes number of a vxfs
> file system?
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:10 CDT