FSSYNC-DEBUG_ERROR(8)
π FSSYNC-DEBUG_ERROR β the fssync-debug error command, but make it make sense
okay bestie, you found the fssync-debug_error page (manual number 8, from the AFS Command Reference) and honestly? it's a whole lot of power in a tiny little command. let's get into it π
β¨ NAME β¨
fssync-debug_error β forces a volume into hard error state, using the FSYNC_VOL_FORCE_ERROR opcode. no cap, that's literally the entire job description. π
πΈ SYNOPSIS πΈ
fssync-debug error -volumeid <volume ID>
[-partition <exact partition name>]
[-reason <sync protocol reason code>]
[-programtype <program type code>]
[-help]
fssync-debug e -v <volume ID>
[-pa <exact partition name>]
[-r <sync protocol reason code>]
[-pr <program type code>]
[-h]
so there's the full-glam version and the speedrun version. same command, shorter letters. pick your vibe β¨
π¦ DESCRIPTION π¦
the fssync-debug error command forces a volume into hard error state. that's it. that's the whole thing. it's giving "no thoughts, just force" π
π OPTIONS π
-volumeid <volume ID>β tells it which volume you mean, by its numeric volume ID. heads up bestie: volume names are NOT permitted here. numbers only, periodt. π’-partition <exact partition name>β the exact partition name, kay? like/vicepa. and no, you cannot abbreviate it. abbreviations are not permitted, do not even try it π-reason <sync protocol reason code>β a numeric sync protocol reason code. where do you find the available codes? they're listed in the OpenAFS source filesrc/vol/fssync_inline.h(iykyk). and if you wantSYNC_REASON_NONE, you pass-reason 0. yes, zero. simple. π-programtype <program type code>β the program type code. the permitted values are exactly:fileServer,volumeUtility,salvager,salvageServer,volumeServerandvolumeSalvager. that's the whole list, don't freestyle it π-helpβ prints the online help for this command. and a fun little detail: all other valid options are ignored when you do this, so it's help time and nothing else. main character energy fr fr π
π PRIVILEGE REQUIRED π
whoever runs this 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 itself. so likeβ¦ not a casual little user account moment. be the root or be quiet π«Ά
π SEE ALSO π
go read these next, bestie, they're the friend group:
fssync-debug_attach(8)fssync-debug_detach(8)fssync-debug_online(8)fssync-debug_offline(8)fssync-debug_leaveoff(8)fssync-debug_callback(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, and it's based on documentation from Steven Jenkins, Tom Keiser and Simon Wilkinson. giving credit where credit is due, always π«‘
and that's the whole page, bestie!! sourced from OpenAFS, dated 2026-07-27, living at FSSYNC-DEBUG_ERROR(8). go forth and force some volumes into hard error state (responsibly, as root, on the actual file server) πβ¨
π¦ 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