Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-22
Checking and Repairing Fileset Integrity
7. Delete all the files beneath the mount point with the OSS shell rm -r command.
This step:
•
Prevents the OSS file system from using the old catalog entries when one of
these files is accessed.
•
Empties the corresponding ZYQ subvolume so that subsequent use of the SCF
DIAGNOSE FILESET command does not inappropriately restore the files to
the lost+found directory of the fileset.
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 on page 5-38 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 on
page 5-21.
2. Remove the disk volume from its current fileset, using the procedure described in
Removing a Disk Volume From a Fileset on page 5-21.
3. Add the disk volume to the storage-pool file of the appropriate fileset, using the
procedure described under Changing the Fileset Catalog on page 5-20.
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 on page A-6.