Administers disk space used for caching file systems with the Cache File-System (CacheFS).
cfsadmin -c cache_directory
cfsadmin -d [ all ] cache_directory
cfsadmin -s [ all ] cache_directory
cfsadmin -u
The cfsadmin command provides the following functions:
For each form of the command, unless the -u flag is specified, you must specify a cache directory, that is, the directory under which the cache is actually stored. A path name in the front file system identifies the cache directory. For the of the command, you must specify a mount point.
You can specify a cache ID when you mount a file system with CacheFS, or you can let the system generate one for you. The -l flag includes the cache ID in its listing of information. You must know the cache ID to delete a cached file system.
You can specify the following cacheFS resource parameters as arguments to
the -o flag. Separate multiple parameters with
commas.
maxblocks=n | Maximum amount of storage space that CacheFS can use, expressed as a percentage of the total number of blocks in the front file system. If CacheFS does not have exclusive use of the front file system, there is no guarantee that all the space the maxblocks parameter allows will be available. The default is 90. |
minblocks=n | The minimum amount of storage space, expressed as a percentage of the total number of blocks in the front file system, that CacheFS is always allowed to use without limitation by its internal control mechanisms. If CacheFS does not have exclusive use of the front file system, there is no guarantee that all the space the minblocks parameter attempts to reserve will be available. The default is 0. |
threshblocks=n | A percentage of the total blocks in the front file system beyond which CacheFS cannot claim resources once its block usage has reached the level specified by minblocks.The default is 85. |
maxfiles=n | Maximum number of files that CacheFS can use, expressed as a percentage of the total number of inodes in the front file system. If CacheFS does not have exclusive use of the front file system, there is no guarantee that all the inodes the maxfiles parameter allows will be available. The default is 90. |
minfiles=n | Minimum number of files, expressed as a percentage of the total number of inodes in the front file system, that CacheFS is always allowed to use without limitation by its internal control mechanisms. If CacheFS does not have exclusive use of the front file system, there is no guarantee that all the inodes the minfiles parameter attempts to reserve will be available. The default is 0. |
threshfiles=n | A percentage of the total inodes in the front file system beyond which CacheFS cannot claim inodes once its usage has reached the level specified by minfiles. The default is 85. |
maxfilesize==n | Largest file size, expressed in megabytes, that CacheFS is allowed to cache. The default is 30. |
Note: You cannot decrease the block or inode allotment for a cache. To decrease the size of a cache, you must remove it and create it again with different parameters.
cfsadmin -c /cache
cfsadmin -c -o maxblocks=60,minblocks=40,threshblocks=50 /cache1
cfsadmin -u -o maxfilesize=2 /cache2
cfsadmin -l /cache3
cfsadmin -d 23 /cache3
cfsadmin -d all /cache3
cfsadmin
The mount command and fsck_cachefs command.