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

5. Create a fileset named HOME, using a unique OSS name server, that has a DEVICELABEL of
000001. The use of multiple OSS name server processes can improve overall performance
if the default name server, $ZPNS, is very busy.
a. Start SCF.
b. Add a new OSS name server for the new fileset:
ADD SERVER $ZPMON.#ZPN1, CPU 1, BACKUPCPU 0
c. Add the new fileset:
ADD FILESET $ZPMON.HOME, DEVICELABEL 000001, &
CATALOG $OSS, BUFFERED LOG, POOL POOL, &
NAMESERVER #ZPN1, MNTPOINT /home
d. Start the new fileset:
START FILESET $ZPMON.HOME
6. Copy all files and directories from the old /home directory into the new fileset using the OSS
shell cp command:
cp -pR /homex/* /home
The -p flag preserves the original permissions and ownership of the files. If you do not specify
this flag, the copied files are owned by the super ID.
NOTE: If you have the SUID or SGID bits set for any file in this fileset, the cp operation
does not preserve those settings and you must set those bits again manually.
You can verify the results of the copy by using the following OSS shell commands:
cd /homex
ls -lR * > /tmp/homex.list
cd /home
ls -lR * > /tmp/home.list
diff /tmp/home.list /tmp/homex.list
If the copy was executed correctly, the diff command produces no output, meaning that the
two directories are identical.
7. Remove the /homex directory and all files and directories underneath it:
rm -r /homex
8. Restore the security permissions that you recorded from the /homex directory to the new
/home directory:
chmod 744 /home
Cleaning Up a Fileset
No OSS Monitor command exists to clean up unused inode entries in a fileset. The procedure to
move files into their own filesets does not reduce the number of inode entries in the original (source)
fileset. Rearranging filesets alone might not improve the performance of the SCF DIAGNOSE
FILESET command on an affected fileset. To clean up the inode entries for a fileset, the fileset must
be removed and reinstalled.
The following example, which uses a fileset called HOME, shows how to eliminate extraneous
inode entries in the ROOT fileset. You must follow this same procedure for every fileset within the
ROOT hierarchy except the ROOT fileset itself:
1. In SCF, stop the HOME fileset by using the following commands:
STOP FILESET $ZPMON.HOME
2. Use pax from an OSS shell prompt to back up the ROOT fileset. The HOME fileset is stopped,
so it is not included in this backup. HP recommends that you make multiple copies of this
backup. For more information, see “Creating a pax Backup of OSS Files in the Guardian File
System” (page 190).
168 Managing Filesets