FS_FLUSHMOUNT(1)
β¨ FS_FLUSHMOUNT π
okay bestie, welcome to the AFS Command Reference π (yes that's the manual name, we're just vibing in it). This one is fs_flushmount and it's literally the "throw out the corrupted mount point" button. Let's get into it π«Ά
πΈ NAME πΈ
fs_flushmount β forces the Cache Manager to discard a mount point β¨
π¦ SYNOPSIS π¦
fs flushmount [-path <dir/file path>+] [-help]
fs flushm [-p <dir/file path>+] [-h]
π DESCRIPTION π
so the fs flushmount command removes from the cache all information associated with each mount point named by the -path argument. Poof. Gone. β¨
The next time an application accesses the mount point, the Cache Manager fetches the most current version of it from the File Server. And the important plot twist: data cached from the associated volume is not affected β this is mount point info only, bestie, don't panic π
The intended use here is to discard information about mount points that has gone and gotten corrupted in the cache π₯΄ (The Cache Manager periodically refreshes cached mount points, but the only other way to discard them immediately is to reinitialize the Cache Manager by rebooting the machine. ikr. so dramatic π)
What does a corrupted mount point look like? Symptoms include:
- garbled output from the
fs lsmountcommand π - failed attempts to change directory to or list the contents of a mount point
π Want to flush cached data rather than a mount point? Different command, bestie β usefs flushorfs flushvolume.
π OPTIONS π
-path <dir/file path>+β names each mount point to flush from the cache. Partial pathnames are interpreted relative to the current working directory, which is also the default value if this argument is omitted π-helpβ prints the online help for this command. All other valid options are ignored. it's giving "help me help you" π
π EXAMPLES π
The following command flushes from the cache the mount point for user "pat"'s home directory:
% fs flushm /afs/example.com/usr/pat
periodt. the mount point is GONE, the home directory is fine π
π PRIVILEGE REQUIRED π
No random walk-ins allowed, sorry bestie β the issuer must have the "l" (lookup) permission:
- on the ACL of the root directory of the volume that houses the file or directory named by the
-pathargument, and - on the ACL of each directory that precedes it in the pathname π«Ά
π₯ 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. legends only, no cap π
okay that's the whole page π this came from OpenAFS, the version is dated 2026-07-27, and honestly? she ate. fs flushmount is the main character, the corrupted mount point is the villain, and you're now fully caught up π
β¨ bye bestie π¦
π¦ 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