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

8. Restore the previously archived files to the mount point using the OSS shell pax command.
For example:
pax -rvf oss_files.pax
9. If the catalog disk volume for the fileset is on the removed disk volume, use the SCF ALTER
FILESET command to enter a new name for the catalog disk volume of the fileset.
This change causes current catalog files to be moved to the specified new disk volume;
previously saved catalog files (with file identifiers of the form PXINnnnn, PXLInnnn, and
PXLOnnnn) are not moved. The subvolume name of the catalog files is not changed.
10. Use the Guardian CVT utility described under “Managing and Repairing Fileset Catalog Files”
(page 170) to purge the saved catalog files (with file identifiers of the form PXINnnnn, PXLInnnn,
and PXLOnnnn) from the old catalog disk volume.
You can now physically remove the disk volume.
Moving a Disk Volume to Another Fileset
To move a disk volume from one fileset to another:
1. Remove the disk volume from the storage-pool file for its current fileset, using the procedure
described under “Removing a Disk Volume From a Storage-Pool File” (page 158).
2. Remove the disk volume from its current fileset, using the procedure described in “Removing
a Disk Volume From a Fileset” (page 158).
3. Add the disk volume to the storage-pool file of the appropriate fileset, using the procedure
described under “Changing the Fileset Catalog” (page 157).
Checking and Repairing Fileset Integrity
This subsection describes use of the SCF DIAGNOSE FILESET command, which runs the Guardian
FSCK utility. The FSCK utility checks and optionally repairs the integrity of an OSS fileset. FSCK
issues EMS events at the start of each diagnostic operation, every 5 minutes during the operation,
and at the end of the operation; see “FSCK Messages” (page 339).
The DIAGNOSE FILESET command corresponds to the fsck command of many UNIX systems.
Only super-group users (255,nnn) can use the DIAGNOSE FILESET command.
When Do You Need to Check Fileset Integrity?
You diagnose a fileset to make sure that you can read and write files in it.
The Guardian FSCK utility looks at every regular file to verify that it has both a directory entry and
data. FSCK makes sure that the superblock, inodes, and catalog files are consistent. You can
choose to repair all inconsistencies or only the serious ones.
Open System Services was designed to allow customers to configure systems where FSCK should
never need to run, even in most multiple-failure situations. Traditional UNIX systems are different:
those systems have relied on running fsck whenever there is a system failure.
FSCK is provided as part of Open System Services primarily to be used in the event of catastrophic
failures such as the following:
• The complete loss of a disk volume containing OSS files or an OSS catalog (loss of both
primary and mirror drives)
• The failure of the built-in recovery mechanisms of an OSS name server
In most of these cases, FSCK is run automatically by the OSS Monitor. Cases where you must run
FSCK manually are signaled by Event Management Service (EMS) OSS subsystem message 3. For
more information about EMS operator messages, see the Operator Messages Manual.
Filesets that are configured with the BUFFERED CREATE (fast-create) option require more frequent
use of FSCK. For such filesets, you must run FSCK when a double failure results in the loss of either
Checking and Repairing Fileset Integrity 159