How to Stop CacheFS Logging
Use the cachefslog -h option to stop logging.
$ cachefslog -h /mount-point |
The following example shows how to stop logging on /home/stuff.
$ cachefslog -h /home/stuff not logged: /home/stuff |
If you get a system response other than the one specified here, you did not successfully stop logging. Check to see if you are using the correct log file name and mount point.
How to View the Working Set (Cache) Size
You might want to check if you need to increase the size of the cache or determine what the ideal cache size is based on your activity since you last used the cachefslog command for a particular mount point.
Become superuser on the client system.
View the current cache size and highest logged cache size.
# cachefswssize log-file-path
For more information, see cachefswssize(1M).
Example--Viewing the Working Set (Cache) Size
In the following example, the end size is the size of the cache at the time you issued the cachefswssize command. The high water size is the largest size of the cache during the time frame in which logging occurred.
# cachefswssize /var/tmp/samlog
/home/sam
end size: 10688k
high water size: 10704k
/
end size: 1736k
high water size: 1736k
/opt
end size: 128k
high water size: 128k
/nfs/saturn.dist
end size: 1472k
high water size: 1472k
/data/abc
end size: 7168k
high water size: 7168k
/nfs/venus.svr4
end size: 4688k
high water size: 5000k
/data
end size: 4992k
high water size: 4992k
total for cache
initial size: 110960k
end size: 30872k
high water size: 30872k
|
Viewing CacheFS Statistics
You might want to view certain information about a specific CacheFS file system. The following table explains the terminology that is displayed in the statistics output.
Table 40-2 CacheFS Statistics Terminology
Output Term | Description |
|---|---|
cache hit rate | The rate of cache hits versus cache misses, followed by the actual number of hits and misses. A cache hit occurs when the user wants to perform an operation on a file or files, and the file or files are actually in the cache. A cache miss occurs when the file is not in the cache. The load on the server is the sum of cache misses, consistency checks, and modifications (modifies). |
consistency checks | The number of consistency checks performed, followed by the number that passed, and the number that failed. |
modifies | The number of modify operations; for example, writes or creates. |
How to View CacheFS Statistics
View the statistics with the cachefsstat command. You can view the statistics at any time. For example, you do not have to set up logging in order to view the statistics.
$ cachefsstat /mount-point |
/mount-point specifies the CacheFS file system for which you want to view the statistics.
If you do not specify the mount point, statistics for all mounted CacheFS file systems will be displayed.
For more information, see cachefsstat(1M).
Example--Viewing CacheFS Statistics
This example shows how to view statistics on the cached file system, /home/sam.
$ cachefsstat /home/sam cache hit rate: 73% (1234 hits, 450 misses) consistency checks: 700 (650 pass, 50 fail) modifies: 321 garbage collection: 0 |