Veritas™ File System 5.0.1 Administrator's Guide

See the sam(1M) and kctune(1M) manual pages.
You can also add an entry to the system configuration file as shown in the following
example:
vxfs_maxlink vx_maxlink 40000
This sets the value of vx_maxlink to 40,000 links.
VxFS inode free time lag
In VxFS, an inode is put on a freelist if it is not being used. The memory space for
this unused inode can be freed if it stays on the freelist for a specified amount of
time. The vx_ifree_timelag tunable specifies the minimum amount of time an
unused inode spends on a freelist before its memory space is freed.
The vx_ifree_timelag tunable is dynamic. Any changes to vx_ifree_timelag
take effect immediately.
The default value of vx_ifree_timelag is 0. By setting vx_ifree_timelag to 0,
the inode free time lag is autotuned to 1800 seconds. Specifying negative one (-1)
stops the freeing of inode space; no further inode allocations are freed until the
value is changed back to a value other than negative one.
You can change the value of vx_ifree_timelag using the sam or kctune commands.
See the sam(1M) and kctune(1M) manual pages.
You can also add an entry to the system configuration file. The following example
changes the value of vx_ifree_timelag to 2400 seconds:
# kctune -s vxfs_ifree_timelag=2400
Note: The default value of vx_ifree_timelag typically provides optimal VxFS
performance. Be careful when adjusting the tunable because incorrect tuning can
adversely affect system performance.
Monitoring free space
In general, VxFS works best if the percentage of free space in the file system does
not get below 10 percent. This is because file systems with 10 percent or more
free space have less fragmentation and better extent allocation. Regular use of
the df command to monitor free space is desirable.
See the df_vxfs(1M) manual page.
VxFS performance: creating, mounting, and tuning file systems
Monitoring free space
48