nfs41_discov...ver_trunking(9)
π nfs41_discover_server_trunking β a.k.a. the "is this the same server or not" vibe check
okay so bestie, you're in the Kernel API Manual, section 9 (kernel routines, iykyk). Buckle up π
β¨ NAME β¨
nfs41_discover_server_trunking β Detect server IP address trunking (mv1) π¦
Like, it figures out whether two things that look different are actually the same server. Main character detective energy, fr fr.
πΈ SYNOPSIS πΈ
int nfs41_discover_server_trunking (struct nfs_client *clp , struct nfs_client **result , const struct cred *cred );
π«Ά ARGUMENTS π«Ά
clpβ thenfs_clientunder test. She's the one being examined πresultβ OUT param: the foundnfs_client, orclp. So like, a pointer gets planted here β either the one we discovered or the original we walked in with πcredβ the credential to use for the trunking test. Gotta have your ID ready for the vibe check π₯
π DESCRIPTION π
Returns NFS4_OK, a negative errno, or a negative NFS4ERR status β three possible outcomes, no in-between, periodt.
If NFS4_OK is returned, an nfs_client pointer is planted in "result". Yup, that's the whole deal. Slay π
β NOTE β
Lowkey important bestie: the returned client may not yet be marked ready. So don't go treating it like it's fully cooked, ngl π
π SEE ALSO π
Kernel file ./fs/nfs/nfs4state.c, plus these iconic siblings:
nfs4_get_renew_cred(9)nfs4_get_clid_cred(9)nfs4_get_state_owner(9)nfs4_put_state_owner(9)nfs4_purge_state_owners(9)nfs4_free_state_owners(9)nfs4_schedule_migration_recovery(9)nfs4_schedule_lease_moved_recovery(9)nfs4_discover_server_trunking(9)
that's the whole page bestie, go be iconic with it π§π
β xoxo, the kernel docs girlie π Β· source: ./fs/nfs Β· dated October 2026 Β· nfs41_discover_server_trunking(9) signing off π«
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms