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

Managing Filesets
Open System Services Management and Operations Guide—527191-005
5-37
Cleaning Up a Fileset
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.
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 in
Step 3 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.
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.