FSSYNC-DEBUG(8)

📦
version 1.8.16.1 · 10 versions
, in ubuntu stonking

💅 FSSYNC-DEBUG — ok bestie, listen up

So this is the manual page for fssync-debug, and also dafssync-debug, from the AFS Command Reference. Basically it's the intro page for the whole fssync-debug command suite. Buckle up. 🎀

✨ NAME ✨

fssync-debug, dafssync-debug — Introduction to the fssync-debug command suite

🦋 DESCRIPTION 🦋

Okay so the fssync-debug command suite is your backstage pass for low-level inspection and control of the file server volume packages. And dafssync-debug? It's literally the exact same command suite, no cap — the only difference is it's built with demand-attach support. Twins. 👯

Now here's the part where I hold your hand, bestie. This command suite operates at an extremely low-level, and it requires detailed knowledge of the OpenAFS architecture and code. You gotta understand the OpenAFS volume finite-state machine before you go messing with the state of a volume. That's not optional, that's the vibe check. 🧚

⚠️ Indiscriminate use of fssync-debug or dafssync-debug in control mode can lead to extremely bad things occurring. Use with care. 😭 Like, fr fr. This is the "main character energy gone wrong" warning.

💖 OPTIONS 💖

So the following arguments and flags are available on many commands in the fssync-debug suite. Every command's own reference page lists them too, but here they're explained in more detail than anywhere else. You're welcome. 🫶

  • -volumeid <volume ID> — Specifies the numeric volume ID. And no, you can't use volume names here. Numeric only. Volume names are not permitted. 🚫
  • -partition <exact partition name> — Specifies the exact partition name (e.g. /vicepa). Abbreviations are not permitted — it's giving "exact match or nothing", and honestly? Respect. ✨
  • -reason <sync protocol reason code> — Specifies a numeric sync protocol reason code. The available codes are listed in the OpenAFS source file src/vol/fssync_inline.h. Oh, and for SYNC_REASON_NONE, you use -reason 0. Write that down. 📝
  • -programtype <program type code> — Specifies the program type code. The permitted values are fileServer, volumeUtility, salvager, salvageServer, volumeServer and volumeSalvager. Six options, all icons. 👑

🔐 PRIVILEGE REQUIRED 🔐

The issuer must have write access to the file server. And usually? That means the issuer must be the local superuser "root" on the file server machine. So yeah, this is a root-girlies-only situation. 👑

🌈 SEE ALSO 🌈

Go read these too, bestie — they're all part of the family:

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. Credit where credit is due, periodt. 💜

and that's the whole page, bestie — mwah! 💖✨

This has been the OpenAFS rendition, dated 2026-07-27, of FSSYNC-DEBUG(8) from the AFS Command Reference. Stay safe out there in the volume finite-state machine. 🦋🎀

📦 where this page comes from