Common Misconfigured HP-UX Resources (April 2006)

# vxfsstat -v / | grep ifree

vxi_ic 1035 18ache_recycleage vxi_ifree_timelag 00

sstat -v / | grep -i curino

16:34:43 MDT 2003

vxi_icache_curino 127526 vxi_icache_inuseino 635

vxi_icache_curino 127101 vxi_icache_inuseino 635

Not

fter being idle all evening, the next day, the number of inodes in the inode cache were reduced

vxi_icache_curino 3011 vxi_icache_inuseino 636

The size of the individual inodes varies depending on the release. Prior to JFS 3.3, the vnode (virtual

d above, the

onsider the JFS 3.5 case again. The system begins to free the inodes if they have been inactive for

0 minutes (1800 seconds) or more. About 30 minutes after entering the find command, the inodes 3

start to free up:

# date; vxf

Thu May 8

e vxfsstat command is executed again 134 seconds later:

# date; vxfsstat -v / | grep -i curino

Thu May 8 16:36:57 MDT 2003

e that 425 inodes were freed in 134 seconds, about 3 inodes per second.

down again as all the inactive files were freed:

# date; vxfsstat -v / | grep -i curino

Fri May 9 14:45:31 MDT 2003

Determining the Memory Cost Associated with each JFS Inode

file system node) and inode were allocated together as a single resource. On JFS 3.3 an

vnode is allocated separately from the inode. On a 32-bit operating system, the inode is smaller as

the pointer fields are only four bytes. On a 64-bit operating system, the pointer fields are eight bytes.

The kernel memory allocator also impacts the amount of space used when allocating the inodes and

associated data structures. You can only allocate memory using certain sizes. For example, if the

kernel tries to allocate an 80-byte structure, the allocator may round the size up to 128 bytes, so that

all allocations in the same memory page are of the same size.

For each inode, you also need to account for locking structures that are also allocated separately from

the inode.