FS_FLUSHVOLUME(1)

πŸ’– FS_FLUSHVOLUME(1) πŸ’–

okay bestie, welcome to the AFS Command Reference β€” this is the page for fs_flushvolume, and no, it is not the same as your regular fs flush, we'll get there, breathe 🫢


✨ NAME ✨

fs_flushvolume β€” literally forces the Cache Manager to throw away cached data from a volume. it's giving spring cleaning for your cache πŸ§ΉπŸ’…


🌸 SYNOPSIS 🌸

fs flushvolume [-path <dir/file path>+] [-help]

fs flushv [-p <dir/file path>+] [-h]

so flushv is the short lil nickname, -p is -path's short form, and -h is -help's. slay πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea: fs flushvolume goes into the cache and removes all data that was fetched from the same volume as each directory or file you name. every one of them. yes, the whole volume's worth.

BUT β€” and this is the important part β€” it does not discard cached status information. only the data. not the whole vibe, just the snacks πŸ™ˆ

so the next time an application asks for data from a flushed directory or file, the Cache Manager goes and fetches the most current version from a File Server, and it brings along a new callback (if necessary) plus associated status information. fresh data, fresh start ✨

now, this command has no effect on two types of data, and bestie you need to internalize these:

  • Data in application program buffers. πŸ₯²
  • Data that has been changed locally and written to the cache but not yet written to the copy on the file server machine. 🚨
so like, if you edited something and it's chilling in the cache unsaved to the server β€” fs flushvolume will not save you. it's not a backup. periodt.

wanna discard the data and the status information for individual files and directories? that's a different command β€” use fs flush (ngl, the naming is a little unhinged, iykyk).

wanna flush a corrupted mount point? use fs flushmount. different tool, different job πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • -path <dir/file path>+ β€” names a file or directory from each volume you want to nuke all the cached data out of. partial pathnames get interpreted relative to the current working directory, and that cwd is also the default value if you just... don't pass this argument at all. no thoughts, head empty, cwd it is 🫢
  • -help β€” prints the online help for this command. and it's iconic for this: all other valid options are ignored when this is around. -help is the main character, everyone else is a background extra πŸ‘‘

🌈 EXAMPLES 🌈

the following command flushes from the cache all data fetched from the volume that contains the current working directory:

% fs flushvolume

look at it go. no paths, no problem. cwd says "i got this" πŸ’–


πŸ‘‘ PRIVILEGE REQUIRED πŸ‘‘

the issuer (that's you, bestie) 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 -path argument, and
  • the ACL of each directory that precedes it in the pathname.

so like, the whole path needs to know you. you can't just walk in πŸ’…


πŸ’œ SEE ALSO πŸ’œ


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 page, babes πŸŽ€ this was FS_FLUSHVOLUME(1) from the AFS Command Reference, brought to you by OpenAFS and dated 2026-07-27. go forth and flush responsibly, ily, mwah πŸ’–βœ¨πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from