nfs4_proc_fsid_present(9)

💅 nfs4_proc_fsid_present(9) 💅

okay so this page is straight out of the Kernel API Manual, and it's all about checking whether an FSID is present or absent on the server. bestie, it's giving filesystem detective energy 🔍✨

🌸 NAME 🌸

nfs4_proc_fsid_present — Is this FSID present or absent on server? 🕵️‍♀️

✨ SYNOPSIS ✨

int nfs4_proc_fsid_present (struct inode *inode , const struct cred
       *cred );

so it returns an int, and you're passing in an inode plus a cred. simple as that, no cap 💅

🎀 ARGUMENTS 🎀

• inode — the inode on the FSID you wanna check. this is the main character of the vibe check 🌟
• cred — the credential to use for this operation. gotta show the server your ID, iykyk 🪪✨

🦋 DESCRIPTION 🦋

the server straight-up tells you whether the FSID is present, moved, or not recognized. no guessing, the server's got the tea ☕👀

this operation is necessary to clear a LEASE_MOVED condition for this client ID. so yeah, it's lowkey important — it's the "bestie, the lease moved, let's fix this" move 🧹💫

here's the return-value vibe check:

• returns NFS4_OK if the FSID is present on this server ✅
• returns -NFS4ERR_MOVED if the FSID is no longer present 🚚😭
• returns a negative NFS4ERR code if some error occurred on the server 💀
• returns a negative errno if a local failure occurred 🛠️🙈

💖 SEE ALSO 💖

Kernel file ./fs/nfs/nfs4proc.c — plus the whole squad of related references:

• nfs41_check_expired_locks(9)
• nfs41_check_open_stateid(9)
• nfs4_proc_get_rootfh(9)
• nfs4_proc_setclientid(9)
• nfs4_proc_setclientid_confirm(9)
• nfs4_proc_get_locations(9)
• nfs4_test_session_trunk(9)
• nfs41_test_stateid(9)
• nfs41_free_stateid(9)

go read those if you're nosy like me, bestie 📚👀

---

— your girl at source/version ./fs/nfs, dated October 2026 🫶✨💖