VOS_SYNCVLDB(1)

📦
version 1.8.16.1 · 10 versions
, in ubuntu stonking

✨ VOS_SYNCVLDB ✨

okay bestie, welcome to the vos_syncvldb page from the AFS Command Reference 💖 this one's a lil admin queen, she checks ur VLDB and makes sure it's not lying about where ur volumes live. very much giving "trust but verify" energy. let's go 🦋

🌸 NAME 🌸

vos_syncvldb — verifies VLDB entries for volumes residing at a specified site, no cap 💅

🎀 SYNOPSIS 🎀

vos syncvldb [-server <machine name>]
    [-partition <partition name>]
    [-volume <volume name or ID>]
    [-dryrun] [-cell <cell name>]
    [-noauth] [-localauth]
    [-verbose] [-encrypt] [-noresolve]
    [-config <config directory>]
    [-help]

vos syncv [-s <machine name>]
    [-p <partition name>]
    [-vo <volume name or ID>]
    [-d] [-c <cell name>]
    [-noa] [-l] [-ve] [-e] [-nor]
    [-co <config directory>]
    [-h]

like, you can spell everything out or use the lil short forms, whichever vibe u prefer ✨

💖 DESCRIPTION 💖

so the whole point of vos syncvldb is: it checks that the status of the volumes sitting either on all the partitions of the file server machine u named with the -server argument, or on the one single partition u named with both -server and -partition, is actually recorded correctly in the VLDB. it's a vibe check for ur database 🔥

and if u also pass -volume to point at one specific volume, then it only compares that one volume's status on the file server machine against its VLDB entry. very targeted, very main character.

k so if u DON'T include -volume: the command interpreter goes and gets a list of the volumes that live on each partition from the Volume Server, then edits the VLDB as needed so it matches what's actually on the partition. for example, if it finds a volume and the VLDB entry is missing or incomplete, it creates or updates one — slay. BUT 🙈 if there's already a VLDB entry that says the volume is somewhere else, or there are irreconcilable conflicts with other VLDB entries, then instead it just writes a message about the conflict to the standard error stream. dramatic but fair. and the command never removes volumes from the file server machine. it does not delete, periodt.

to get complete VLDB consistency, run this command on every file server machine in the cell, and then run the vos syncserv command on every file server machine in the cell. both. in that order-ish. the way that these two are a duo 😭🫶

ngl, using -volume basically smashes this command's effects together with vos syncserv's effects, but for a single volume only. it doesn't just verify that the VLDB entry is correct for the volume type u specified (read/write, backup, or read-only) — it ALSO checks that every related volume type mentioned in that VLDB entry actually exists at the site listed in the entry. iconic. and here's the tea: u don't have to give the -server argument (or optionally, the -partition argument) — but if u give one or both of them, the results are only reliable if they specify the actual real location of the volume that -volume pointed at. fr fr, no shortcuts 💀

✨ OPTIONS ✨

  • -server <server name> — names the file server machine that's housing the volumes u wanna verify VLDB entries for. u can give the machine's IP address or its host name (fully qualified, or an unambiguous abbreviation works too). for the deets, see vos(1).
  • -partition <partition name> — names the partition that's housing the volumes u wanna verify VLDB entries for. u gotta give the -server argument along with this one, okay? give the partition's complete name with the preceding slash (like, for example, "/vicepa") or use one of the three acceptable abbreviated forms. details live in vos(1).
  • -volume <volume name or ID> — specifies the name or the volume ID number of a single volume whose VLDB entry u wanna verify. this argument can be combined with the -server argument (and optionally the -partition argument). mixing and matching, we love to see it 🎀
  • -dryrun — shows u the actions that would be taken, but does not actually make any changes. window shopping only, bestie 👀
  • -cell <cell name> — names the cell in which to run the command. do NOT combine this argument with the -localauth flag. more details in vos(1).
  • -noauth — assigns the unprivileged identity "anonymous" to the issuer. do NOT combine this flag with the -localauth flag. more details in vos(1).
  • -localauth — constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. the vos command interpreter presents it to the Volume Server and the Volume Location Server during mutual authentication. do NOT combine this flag with the -cell argument or the -noauth flag. more details in vos(1).
  • -verbose — produces a detailed trace of the command's execution on the standard output stream. if u omit this argument, only warnings and error messages show up. quiet luxury 💅
  • -encrypt — encrypts the command so that the operation's results are not transmitted across the network in clear text. this option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. secure girly behavior 🔒
  • -noresolve — shows all servers as IP addresses instead of the DNS name. this is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. this option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later.
  • -config <configuration directory> — set the location of the configuration directory to be used. this defaults to /etc/openafs, EXCEPT if -localauth is specified, in which case the default is /etc/openafs/server. this option lets u use alternative configuration locations for testing purposes, cute 🧚
  • -help — prints the online help for this command. all other valid options are ignored. she said "nope, just the help" 🙈

🌈 EXAMPLES 🌈

this example command verifies the VLDB entry for each volume stored on the file server machine "fs4.example.com". look at her go:

% vos syncvldb fs4.example.com

👑 PRIVILEGE REQUIRED 👑

the issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument and on each database server machine. and if the -localauth flag is included, then the issuer must instead be logged on to a server machine as the local superuser "root". that's the whole dress code, no exceptions 💅

🔥 SEE ALSO 🔥

vos(1), vos_syncserv(1)

go read those too, they're the rest of the lore 💖

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

this documentation is covered by the IBM Public License Version 1.0. it was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

okay that's the whole page bestie, u ate that 🍓 this was OpenAFS, dated 2026-07-27, and the manual page goes by VOS_SYNCVLDB(1) — stan a well-documented sync command, mwah 💋✨

📦 where this page comes from