AIX Version 4.3 Differences Guide

Parameter
threshblocks=n
maxfiles=n
minfiles=n
maxfilesize=n
Description
A percentage of the total blocks in the front file system beyond
which, CacheFS cannot claim resources once its block usage
has reached the minblocks level. Default=85%
Maximum number of files that CacheFS can use, expressed as
a percentage of the total number of inodes in the front file
system. Default=90%
Minimum number of files that CacheFS is always allowed to
use, expressed as a percentage of the total number of inodes in
the front file system. Default=0%
Largest file size, expressed in megabytes, that CacheFS is
allowed to cache. Default=3
fsck_cachefs
The fsck_cachefs command checks the integrity of cached file systems. By default
it corrects any CacheFS problems it finds. Unlike the standard fsck command
there is no interactive mode.
The fsck_cachefs command syntax is:
fsck -F cachefs [ -m | -o noclean ] cache_directory
Table 42 provides the available flags for this command.
Table 42. fsck_cachefs Options
Flag
Description
-m Check, but do not repair.
-o noclean Force a check on the cache even if there is no reason to
suspect there is a problem.
cache-directory
The name of the directory where the cache resides.
The following example shows the actions required to allow an NFS client machine
to mount the remote filesystem /images from the server aix4xdev and use the
CacheFS mechanism to improve performance.
The /images filesystem on the server is a large filesystem, so a dedicated JFS
will be used to store the local cache.
1. Use SMIT to create a JFS of the required size to act as the cache. For
example, /cacheFS.
2. Mount the JFS to be used for the cache.
mount /cacheFS
Create an empty cache structure to be used as the cache. This is created
using the cfsadmin command. The argument is the name of the cache
directory object you want to create. The object should not exist.
cfsadmin -c /cacheFS/cachedir
186 AIX Version 4.3 Differences Guide