FSSYNC-DEBUG_CALLBACK(8)
π FSSYNC-DEBUG_CALLBACK β the AFS Command Reference, section 8, bestie π
okay so real talk, this one lives in section 8 of the AFS Command Reference, which is the "admin tools, handle with care" corner of the man page universe. it's a debug tool. it breaks callbacks. it is not a chill little command you run for funsies. but it slays at exactly one job and we're gonna learn it together π«Ά
β¨ NAME β¨
fssync-debug_callback β breaks callbacks for a volume, and yes it is literally the FSYNC_VOL_BREAKCBKS opcode in a trench coat π
πΈ SYNOPSIS πΈ
fssync-debug callback -volumeid <volume ID>
[-partition <exact partition name>]
[-reason <sync protocol reason code>]
[-programtype <program type code>]
[-help]
fssync-debug ca -v <volume ID>
[-pa <exact partition name>]
[-r <sync protocol reason code>]
[-pr <program type code>]
[-h]
fssync-debug cbk -v <volume ID>
[-pa <exact partition name>]
[-r <sync protocol reason code>]
[-pr <program type code>]
[-h]
so you got three whole ways to say its name: callback, ca, and cbk β the command is giving "I have many nicknames and I answer to all of them" energy β¨ and every single flag has a glow-down short form too. use whichever one your fingers remember at 3am.
π¦ DESCRIPTION π¦
The fssync-debug callback command breaks callbacks for a volume.
that's it. that's the whole thing. it walks in, it breaks the callbacks for that volume, it leaves. no notes. lowkey iconic honestly.
π OPTIONS π
-volumeid<volume ID> β hands over the numeric volume ID. and bestie, listen: volume names are not permitted. numeric only. do not try to be cute with a name here, it will not work π-partition<exact partition name> β the exact partition name, like/vicepa. abbreviations are NOT permitted β it wants the whole thing spelled out, no shortcuts, no vibes-based guessing π-reason<sync protocol reason code> β the numeric sync protocol reason code. the available codes are listed over in the OpenAFS source filesrc/vol/fssync_inline.h. and forSYNC_REASON_NONE, you use-reason 0. zero. that's your "no reason" reason, iykyk π-programtype<program type code> β the program type code. permitted values arefileServer,volumeUtility,salvager,salvageServer,volumeServerandvolumeSalvager. six options, pick one, no free-styling π-helpβ prints the online help for this command. and here's the gag: all other valid options are ignored. so you can pile on every flag you want and-helpwill simply not care. main character energy fr fr π
π PRIVILEGE REQUIRED π
The issuer must have write access to the file server. usually that means the issuer must be the local superuser root on the file server machine.
so yeah, this is a root-only situation. if you're not root on that box, this command is not for you and it will let you know π
π₯ SEE ALSO π₯
the whole extended fam, go read all of them:
fssync-debug_attach(8)fssync-debug_detach(8)fssync-debug_online(8)fssync-debug_offline(8)fssync-debug_leaveoff(8)fssync-debug_error(8)
π COPYRIGHT π
Copyright 2010 Davor Ocelic <docelic@spinlocksolutions.com>
This documentation is covered by the IBM Public License Version 1.0. This man page was written by Davor Ocelic for OpenAFS, based on documentation from Steven Jenkins, Tom Keiser and Simon Wilkinson.
shoutout to Davor, Steven, Tom and Simon for writing it all down so we could be here today π«Ά
and that's the whole page, bestie β¨ no cap, you now know fssync-debug_callback better than most people know their own wifi password. go break some callbacks responsibly π
OpenAFS β 2026-07-27 β FSSYNC-DEBUG_CALLBACK(8) ππ¦π
π¦ where this page comes from
- ubuntu stonking: openafs-fileserver 1.8.16.1-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms