FS_GETCACHEPARMS(1)
π FS_GETCACHEPARMS(1) π
okay bestie, welcome to the AFS Command Reference β this is the page for fs_getcacheparms, and honestly? it's a vibe. let's get into it π«Ά
β¨ NAME β¨
fs_getcacheparms β shows you the current size of your cache and how much of it you're actually using π
πΈ SYNOPSIS πΈ
fs getcacheparms [-help] [-files] [-excessive]
fs getca [-h] [-files] [-excessive]
π¦ DESCRIPTION π¦
So fs getcacheparms tells you the current size of the cache β and just so you know, that cache can live in memory or on disk, no judgment either way β plus how much of it is in use right now. π
here's the tea though: the stats it reports come straight from kernel memory. so on a machine using a disk cache, the size it reports can differ from whatever you set in the /etc/openafs/cacheinfo file β that happens if somebody used the fs setcachesize command to change the cache size. so don't come for this command when the numbers don't match, it's literally just reporting what the kernel said π
β¨ OPTIONS β¨
-helpβ prints the online help for this command. and bestie, listen: every other valid option gets ignored when you use this one. it's giving solo main character energy π-filesβ shows you the current number of cache files in use and the max that's available, on top of the normal current cache size display. more data, more fun π-excessiveβ the deluxe version. shows detailed cache statistics, including the flags set on each cache element and the distribution of cache entries by size. it's giving data dump and we're obsessed π«Ά
π OUTPUT π
the output reports:
AFS using <amount> of the cache's available <size> 1K byte blocks.
where <amount> is the number of kilobyte blocks currently used to cache data and status info, and <size> is the total current cache size. periodt. β¨
π EXAMPLES π
first up, here's what it looks like on a machine with a 25000 kilobyte cache:
% fs getcacheparms
AFS using 22876 of the cache's available 25000 1K byte blocks.
and here's the output when you ask for file info:
% fs getcacheparm -files
AFS using 0% of cache blocks (897 of 200000 1k blocks)
1% of the cache files (79 of 6250 files)
and finally, here's that detailed info you get with the excessive flag:
% fs getcacheparm -excessive
AFS using 0% of cache blocks (897 of 200000 1k blocks)
1% of the cache files (79 of 6250 files)
afs_cacheFiles: 6250
IFFree: 6171
IFEverUsed: 79
IFDataMod: 0
IFDirtyPages: 0
IFAnyPages: 0
IFDiscarded: 1
DCentries: 3122
0k- 4K: 74
4k- 16k: 3045
16k- 64k: 2
64k- 256k: 0
256k- 1M: 1
>=1M: 0
π PRIVILEGE REQUIRED π
none. zero. you need nothing. we love an accessible queen π
π SEE ALSO π
π§ COPYRIGHT π§
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
and that's the whole page, bestie!! this was OpenAFS, dated 2026-07-27 β thanks for reading, mwah πβ¨ no cap, you understood all of it π¦
π¦ where this page comes from
- ubuntu stonking: openafs-client 1.8.16.1-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms