FSSYNC-DEBUG_VNODE(8)

πŸ’– FSSYNC-DEBUG_VNODE πŸ’–

okay bestie, welcome to the fssync-debug_vnode page β€” that's section 8 of the AFS Command Reference btw, aka the big-girl sysadmin section. sit down, hydrate, and let's get into it ✨

It's the one that shows you vnode info, and it rides on the FSYNC_VOL_QUERY_VNODE opcode. iykyk πŸ’…


🌸 NAME 🌸

fssync-debug_vnode β€” display vnode info (FSYNC_VOL_QUERY_VNODE opcode)

yeah. that's literally it. she shows you stuff about a vnode. iconic. πŸ‘‘


✨ SYNOPSIS ✨

fssync-debug vnode -volumeid <volume ID>
    -vnodeid <vnode ID>
    -unique <uniquifier>
    -partition <exact partition name>
    [-reason <sync protocol reason code>]
    [-programtype <program type code>]
    [-help]

fssync-debug vn -vo <volume ID>
    -vn <vnode ID>
    -u <uniquifier>
    -pa <exact partition name>
    [-r <sync protocol reason code>]
    [-pr <program type code>]

so yes, there are two spellings: the full-word version and the ✨short-flag✨ version, because apparently we're doing nicknames for everything. vnode / vn, -volumeid / -vo, -vnodeid / -vn, -unique / -u, -partition / -pa, -reason / -r, -programtype / -pr. two lanes, same destination, pick your fighter πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

The fssync-debug vnode command displays information about a given vnode.

that's it. that's the whole plot. you point it at a vnode, it spills the tea about that vnode. no cap. 🌸


πŸ’… OPTIONS πŸ’…

  • -volumeid <volume ID> β€” you're telling her the numeric volume ID. heads up bestie: volume names are not permitted here, only numbers. she does not accept nicknames. πŸ™ˆ
  • -vnodeid <vnode ID> β€” the numeric vnode ID. just the number, mwah πŸ’–
  • -unique <uniquifier> β€” the numeric vnode uniquifier. yes it's spelled "uniquifier". yes that's a real word. slay ✨
  • -partition <exact partition name> β€” the exact partition name, like /vicepa. and when they say exact, they MEAN exact β€” abbreviations are not permitted. no shortcuts, no vibes-based guessing, full name only. πŸŽ€
  • -reason <sync protocol reason code> β€” the numeric sync protocol reason code. the available codes are listed in the OpenAFS source file src/vol/fssync_inline.h (go look, bestie, it's all there). and if you want SYNC_REASON_NONE, you use -reason 0. zero. the nothing code. πŸ’€
  • -programtype <program type code> β€” the program type code. the permitted values are fileServer, volumeUtility, salvager, salvageServer, volumeServer and volumeSalvager. that's the whole guest list, nobody else gets in the door. 🌈
  • -help β€” prints the online help for this command. and note: all other valid options are ignored when you ask for help. she's not multitasking. help mode is help mode. periodt. 😌

πŸ‘‘ PRIVILEGE REQUIRED πŸ‘‘

The issuer must have write access to the file server.

usually that means the issuer has to be the local superuser "root" on the file server machine. so like… root energy only. no random accounts waltzing in here pretending. 🫢

fr fr, don't try this without the right access β€” it's giving locked-door-for-a-reason.

🌟 SEE ALSO 🌟

go read those too, they're the rest of the friend group πŸ’œ


Copyright 2010 Sine Nomine Associates

This documentation is covered by the IBM Public License Version 1.0.

This man page was written by Andrew Deason and Davor Ocelic for OpenAFS.


and that's the whole page, bestie 🧚 this was OpenAFS, dated 2026-07-27 β€” written by the OpenAFS girlies, loved by me, understood by you. now go query that vnode. mwah πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from