Printer FriendlyEmail Article Link

Velocity - Inodes and disk space

Velocity 5.0 - Latest.

Velocity Inodes and disk space

Velocity usally generates thousands of files everyday from logs and transactions from the regular use of its services, of course velocity automatically do a lot of cleaning over this files, but there will be cases when some manual cleaning could be needed.

Due this, it is very important to keep an eye on the inodes count and the disk space of a very old or huge enviroment.

The inode (index node) is a data structure in a Unix-style file system that describes a file-system object such as a file or a directory. If you run out of inodes, it does not matter that you still have disk space left you will not be able to make use of the system to store files any longer, which results on a totall stuck state of the sytem.

Running our of disk space is also something to worry about, Velocity by default will start sending low disk space messages when it reaches the 80% of disk usage.

This threshold can be configured to be something near to the 100% or earlier as well.

The solution:

In both cases the solution is to delete not needed files of the system or add more disk space to the Velocity VM or VDS.

Some files that can be deleted are the /data/logs/archive/ *logs*    this probably will take a lot of space and inodes after some time or a lot of usage of velocity.

Adding more space is also a good option in some cases when the space is available, for going this you should:
  • Power off any agent connected to velocity first.
  • Power off Velocity VM.
  • Power off VDS VM.
  • Increase the disk size on the VMware Vsphere hypervisor / KVM console.
  • Power up VDS.
  • Power up Velocity.
  • FInally power up any agent.
Unlikely regular linux systems, Velocity and VDS are prepared to automatically claim the new space without any intervencion from the user or administrator.

You can check the disk space with:

df -h (for disk space)

df -i  (for inodes count) 


Product : Velocity