the relation between %inode and %disk space

[inventsekar_1]

Hi,

the bdf -i result in my 11.11:

Filesystem kbytes used avail %used iused ifree %iuse Mounted on
/dev/vg00/lvol3 4194304 2682320 1505032 64% 10544 47248 18% /
/dev/vg00/lvol1 298928 61736 207296 23% 65 32703 0% /stand
/dev/vg00/lvol8 5242880 2223168 2996360 43% 40049 94351 30% /var
/dev/vg00/lvol7 4194304 1907376 2269104 46% 33155 71453 32% /usr
/dev/vg00/lvol6 1048576 631992 414400 60% 118 13002 1% /tmp
/dev/vg00/lvol5 5120000 3962784 1151176 77% 42814 36162 54% /opt
/dev/vg00/lvol4 2097152 2058864 38288 98% 133 12187 1% /home


i would like to know what is the relation between "%iuse" and "%used" ie %disk used.

for example:
/home %used is 98% and %iuse is 1%

and in one more server, %iuse is 94%. it crossed the threshold value (90%). how much files i need to reduce so that %iuse will reduce?

[James R. Ferguson · Accepted solution]

Hi:

The '%iuse' is the percentage of space needed for inodes. The value would be directly related to the number of files and directories in the filesystem. For a VxFS filesystem, an inode is typically 256 characters long. For any filesystem you can see this with, for example:

# mkfs -F vxfs -m /dev/vg00/lvol4

The structure of a VxFS inode is docueented here:

http://docs.hp.com/en/B2355-60105/inode_vxfs.4.html

Regards!

...JRF...

[spex]

sekar,

Have a look at this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=942681

PCS

[Bill Hassell]

Simple answer: the -i option is useless today. Back 10 or 15 years ago, all filesystems were HFS -- now only /stand is typically an HFS filesystem. In HFS, the number of available inodes is fixed when newfs is run and massively large numbers of small files could use up all the inodes without using up all the disk space.

However, VxFS filesystems make their inodes as required and thus will not run out until the disk is full. The value shown by bdf -i for VxFS %iuse is not meaningful.