VOS_LOCK(1)

πŸ’… VOS_LOCK(1) β€” like, the AFS Command Reference girlies know

okay bestie, welcome to vos_lock, straight out of the AFS Command Reference. sit down, grab a strawberry, we're locking VLDB entries today and it's gonna be iconic ✨


πŸŽ€ NAME

vos_lock β€” locks a VLDB volume entry πŸ”’

πŸ¦‹ SYNOPSIS

vos lock -id <volume name or ID>
    [-cell <cell name>]
    [-noauth] [-localauth]
    [-verbose] [-encrypt] [-noresolve]
    [-config <config directory>]
    [-help]

vos lo -i <volume name or ID>
    [-c <cell name>]
    [-noa] [-l] [-v] [-e] [-nor]
    [-co <config directory>]
    [-h]

πŸ’– DESCRIPTION

so the way that vos lock works is: it locks the Volume Location Database (VLDB) entry for the volume you point at, and that means any operation that needs to write to that entry is just… blocked. doors closed. not today. 🚫

and here's the tea, bestie β€” the lock isn't just for the volume version you named in -id. it applies to all of the volume versions associated with that entry. every single one. the whole squad. πŸ‘‘

wanna unlock just one single VLDB entry? that's vos unlock. wanna unlock a bunch of them, or literally every locked entry in the VLDB? that's vos unlockvldb. slay.

⚠️ CAUTIONS

fr fr, do NOT use this command in normal circumstances. it is not a casual little guy.

it exists for the specific situation where you've got reason to believe volume operations can't properly lock VLDB volume entries the way they normally do to sync up with each other β€” and you wanna guarantee the volume just stays unchanged. that's it. that's the whole use case. do not make it your main character. πŸ™ˆ

✨ OPTIONS ✨

  • -id <volume name or ID> β€” tells it which volume you mean: either the complete name, or the volume ID number, of a volume of any of the three types. bestie, this is the one you actually need.
  • -cell <cell name> β€” names the cell where the command should run. do not combine this with the -localauth flag, okay? more deets in vos(1).
  • -noauth β€” hands the issuer the unprivileged identity "anonymous". do not combine this flag with -localauth. more deets in vos(1).
  • -localauth β€” builds a server ticket using a key from the local /etc/openafs/server/KeyFile file. the vos command interpreter shows 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 deets in vos(1).
  • -verbose β€” spills a detailed trace of the command's execution onto the standard output stream. leave it off and only warnings and error messages show up.
  • -encrypt β€” encrypts the command so the operation's results don't travel across the network in clear text πŸ”. available in OpenAFS versions 1.4.11 or later and 1.5.60 or later.
  • -noresolve β€” shows all servers as IP addresses instead of the DNS name. super handy when the server address is registered as 127.0.0.1, or when you're dealing with multi-homed servers πŸ’€. available in OpenAFS versions 1.4.8 or later and 1.5.35 or later.
  • -config <configuration directory> β€” sets where the configuration directory lives. default is /etc/openafs, except when -localauth is specified, in which case the default is /etc/openafs/server. this option lets you use alternative config locations for testing purposes πŸ§ͺ.
  • -help β€” prints the online help for this command. every other valid option gets ignored, she's not listening πŸ’….

🌸 EXAMPLES

this command locks the VLDB entry for "user.terry":

% vos lock user.terry

and that's it. locked. periodt. πŸŽ€

πŸ‘‘ PRIVILEGE REQUIRED

the issuer has to be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument, and on each database server machine. (yes bestie, the whole set.)

if the -localauth flag is in the mix, then instead the issuer must be logged on to a server machine as the local superuser "root".

πŸ”₯ SEE ALSO

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.


and that's the whole page, bestie 🫢 this was OpenAFS, page dated 2026-07-27 β€” go lock responsibly, mwah πŸ’–

πŸ“¦ where this page comes from