FS_LSMOUNT(1)

💫 FS_LSMOUNT(1) — aka fs lsmount 💫

okay bestie, welcome to the AFS Command Reference corner of the internet 🎀 this one is fs_lsmount(1) and it's genuinely so useful, i'm obsessed.

---

✨ NAME ✨

fs_lsmount — reports the volume for which a directory is the mount point 🫶

---

🌸 SYNOPSIS 🌸

fs lsmount -dir <directory>+ [-help]

fs ls -d <directory>+ [-h]

---

🦋 DESCRIPTION 🦋

so the fs lsmount command tells you which volume each directory you hand it is a mount point for. that's it. that's the job 💅

and if a directory is not a mount point, or it's just not in AFS at all? then it hits you with an error message instead. no vibe, just facts 💀

want to make a mount point? that's fs mkmount, bestie. want to yeet one? that's fs rmmount. we don't do that here, we just look 👀

---

💖 OPTIONS 💖

• -dir <directory>+ — names the directory that's serving as the mount point for a volume. important: the last element in the pathname you give has to be an actual name, not a shorthand thing like one or two periods ("." or ".."). the command said what it said 🙈
• -help — prints the online help for this command. and every other valid option? ignored. literally ghosted. ✨

---

👑 OUTPUT 👑

if the directory you named is a mount point, you get this, and it's giving:

'<directory>' is a mount point for volume '<volume name>'

where:

• a number sign ("#") comes before the <volume name> string for a regular mount point 🔥
• a percent sign ("%") comes before the <volume name> string for a read/write mount point 🔥
• for a cellular mount point, a cell name and a colon (":") follow that number or percent sign, and come before the <volume name> string 🔥

and if you want the full lore on how the Cache Manager reads each of those three types of mount points, go read the fs mkmount reference page. iykyk 🧚

if the directory is a symbolic link pointing at a mount point, the output looks like:

'<directory>' is a symbolic link, leading to a mount point for volume
'<volume name>'

if the directory isn't a mount point, or isn't in AFS, you get:

'<directory>' is not a mount point.

and ngl, if the output comes out garbled?? 😭 it's possible the mount point has become corrupted in the local AFS client cache. the fix is fs flushmount, which discards it and forces the Cache Manager to refetch the mount point. slay, problem solved 💅

---

🌈 EXAMPLES 🌈

here's the mount point for the home directory of user "smith":

% fs lsmount /afs/example.com/usr/smith
'/afs/example.com/usr/smith' is a mount point for volume '#user.smith'

and here's both the regular and the read/write mount points for the Example Corporation cell's "root.cell" volume. iconic duo fr:

% fs lsmount /afs/example.com
'/afs/example.com' is a mount point for volume '#root.cell'

% fs lsmount /afs/.example.com
'/afs/.example.com' is a mount point for volume '%root.cell'

last one, a cellular mount point — the Example Organization cell's "root.cell" volume, mounted inside the Example Corporation cell's tree:

% fs lsmount /afs/example.org
'/afs/example.org' is a mount point for volume '#example.org:root.cell'

---

🎀 PRIVILEGE REQUIRED 🎀

whoever's issuing this command needs the "l" (lookup) permission on the ACL of the root directory of the volume that houses the file or directory named by the -dir argument. and, yeah, also on the ACL of every single directory that comes before it in the pathname. no shortcuts bestie, permission checks all the way down 💜

---

🍓 SEE ALSO 🍓

• fs_flushmount(1)
• fs_mkmount(1)
• fs_rmmount(1)

---

💀 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. giving credit where credit is due, as always 🫶

---

and that's the whole page, bestie 🌸 this was OpenAFS, dated 2026-07-27, and it lives at FS_LSMOUNT(1) — mwah, go check your mount points, you're gonna do great 💅✨