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

Figure 11 Storage Pools and Disk Volumes
While OSS filesets can span multiple physical disk volumes, individual files cannot. Thus if you
allocate for a fileset a disk volume that is running out of space, you might not be able to extend
existing files or write new large files on that volume, even if all other available volumes are nearly
empty.
After a fileset is created, you can check the individual disk volumes in the fileset’s storage-pool file
to monitor the disk space that the fileset is using. If one or more volumes are almost full, you can
make more volumes available for the fileset. To do this, unmount the fileset, add more volumes to
the storage-pool file, and then remount the fileset. From this point on, as that OSS name server for
that fileset continues to create new files, it uses the new disk volumes as well as remaining space
on the other specified volumes.
NOTE: The space allocated for OSS name server catalog files is not expandable; additional
extents cannot be allocated. When the disk on which the catalog resides becomes so full that a
new PXINODE catalog file extent is needed, add one or more filesets so that the inodes are spread
across several PXINODE files.
A sample storage-pool file is shown under “Creating a Storage Pool” (page 145).
Relating OSS Files, Filesets, and Disk Volumes 89