Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

OSS File System Resources Overview
There are four types of OSS File System (OSS FS) resources:
• Memory pools
• Bounded
• Unbounded
• Fileset
Some memory pools are allocated from 32-bit addressable memory and some from 64-bit
addressable memory. The OSS FS products obtain physical memory for these memory pools as
needed. Pool limit errors happen when a memory pool has reached its configured limit. Shortages
of available physical memory can cause pool allocation errors before the memory pool limit is
reached.
There are two general classifications of bounded and unbounded OSS FS resources:
• A bounded resource has its own specific limit that cannot be exceeded. EMS events are
generated when the following “hard limits” occur:
◦ The limit is close to being exceeded (limit warning).
◦ The limit has been reached (limit error).
◦ The usage has fallen sufficiently below the limit (status normal), after a limit warning or
limit error EMS event occurred.
◦ The memory that supports the bounded resource cannot be allocated and a memory
shortage occurs (allocation error).
• An unbounded resource does not have hard limits, but its usage is restricted by:
Memory pool limits◦
◦ The ALL OPENS bounded resource limit of 128,000 total opens per processor
The total number of file opens per processor (ALL OPENS) includes opens of all types:
disk opens, terminal opens, pipe/FIFO opens, AF_INET socket opens, AF_UNIX socket
opens, NFS opens, directory opens, and directory stream opens.
If the memory pool and ALL OPENS limits are not exceeded, the unbounded resources
per-processor “soft limits” can be exceeded. Because unbounded resources can exceed their
soft limits, resource usage EMS events are not generated.
Table 7 lists the memory pool resources of the OSS FS and their per-processor limits. These resources
are viewable in both SCF and the HP NonStop Measure performance monitor.
94 Managing Servers