Open System Services Management and Operations Guide (G06.29+, H06.07+)

Open System Services Management and Operations Guide—527191-005
E-1
E Environment Limits
This appendix summarizes the architectural and functional limits that apply to the Open
System Services environment on NonStop servers. Limits for a specific release version
update (RVU) are subject to increases as software product revisions (SPRs) occur.
OSS application programs that conform to POSIX.1 conform to a set of limits defined
by the POSIX standards; POSIX limits can be less than those imposed by the
environment. Refer to the header files used by a specific application to determine the
current settings of that program’s programmatic limits; for example, most programs use
/usr/include/limits.h.
Table E-1. OSS Environment Limits (page 1 of 5)
Description
Maximum
Value Comment
To Check Amount
Currently Used
OSS files in
one fileset
2.2 million The limiting factor is the
number of inodes used within
the fileset; inodes are used for
any entry in the fileset:
directories, named pipes
(FIFOs), files, AF_UNIX
sockets, and so forth.
Prior to RVU G06.24 (prior to
PVU T8621G11), the limit was
500,000 inodes per fileset.
Prior to RVU G06.18 (prior to
SPR T8621AAU), the limit was
250,000 inodes per fileset.
At a TACL prompt in the
catalog subvolume:
FUP INFO PXINODE,
STAT
gives a rough
approximation; the
PXINODE file groups free
inodes into a single
record.
At an OSS shell prompt,
using the fileset mount
point (mtpt):
ls -W NOG -W NOE -R
mtpt | wc -l
gives a rough
approximation (also skips
free inodes). If the fileset
directory tree contains the
mount point for another
fileset, the inodes of that
fileset will also be listed.
OSS
filename
248
characters
OSS
pathname
1024
characters