NOTICE: /: out of inodes

[stevenriz]

What are these and is it fixable? As it stands I cannot telnet to this machine anymore. I might have to just shut it off unless there is any other way to shut it down gracefully. No console access either.... It is just about to go into service as a Production webserver and I would really lke to fix it asap.
Netra T1 with 256mb RAM.

Ahhhhhhh!

 

[cfsalmeida]

Each file (regular file, directory, sym link etc.) requires an inode and the number of inodes created when the filesystem is first made is dependent on:

1) The size of the filesystem
2) The bytes_per_inode value used by newfs

When a ufs filesystem is created under Solaris using default settings the number of bytes per inode defaults to 2048, this can be changed by using the -i option (see newfs manual page)

Therefore, the number of inodes (and hence number of files that can be created) is given by:

file_system_size_(in_bytes) / bytes_per_inode

So, for 3000 files, the filesystem size must be 3000 x 2048 bytes, ie. a minimum size of 6.1Mb
To increase the number of inodes on / boot from cdrom in single user mode, backup the filesystem unmount it, and use newfs -i <bytes_per_inode> <device> to re-make the filesystem before remounting it and then restoring your data.

Regards,

Carlos Almeida,

 

[stevenriz]

Ouch, that's ugly. We just dumped the box, restarted it and deleted thousands of old files from all file systems. Would you guess that this should do the trick?

Thanks for the expanation!
Steve