VOS_RENAME(1)
β¨ VOS_RENAME(1) β¨
okay so bestie, meet vos_rename, from the AFS Command Reference π this is the little icon that renames a volume, and honestly? it's giving "spring cleaning for your cell" π
πΈ NAME πΈ
vos_rename β renames a volume π
π SYNOPSIS π
vos rename -oldname <old volume name>
-newname <new volume name>
[-cell <cell name>]
[-noauth] [-localauth]
[-verbose] [-encrypt] [-noresolve]
[-config <config directory>]
[-help]
vos ren -o <old volume name>
-ne <new volume name>
[-c <cell name>] [-noa] [-l] [-v] [-e] [-nor]
[-co <config directory>]
[-h]
π DESCRIPTION π
The way that vos rename works is SO simple and I'm obsessed: it takes the read/write volume you named with the -oldname argument and swaps its name to whatever you put in -newname. that's it, that's the whole job π«Ά
and here's the cute part β the names of the read/write's read-only copies and its backup copy, if any exist, change automatically to match. no extra work, they just follow along like loyal little butterflies π¦
β οΈ heads up though! after you run this, remember to fix any mount points that still point at the old volume name. you do that by removing the old mount point with thefs rmmountcommand and then creating a new one with thefs mkmountcommand. don't skip this, bestie, or your mounts will be pointing at a ghost π»
β¨ OPTIONS β¨
-oldname<old volume name or id> β the current name or numeric id of the read/write volume you wanna rename. either one works, we're flexible like that π-newname<new volume name> β the new name you want for the volume.
ik this sounds weird but listen: the new name may be the same as the current volume name in the VLDB, and that's on purpose β you do that to complete a previously interrupted volume rename. finishing what you started, main character energy π₯
-cell<cell name> β names the cell to run the command in. do not combine this argument with the-localauthflag, okay? for more details, seevos(1).-noauthβ assigns the unprivileged identity"anonymous"to the issuer. do not combine this flag with the-localauthflag. for more details, seevos(1).-localauthβ constructs a server ticket using a key from the local/etc/openafs/server/KeyFilefile. thevoscommand interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. do not combine this flag with the-cellargument or the-noauthflag. for more details, seevos(1).-verboseβ produces a detailed trace of the command's execution on the standard output stream. if you omit this argument, only warnings and error messages show up. so if you want the tea, ask for the tea π-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.-noresolveβ shows all servers as IP addresses instead of the DNS name. this is very useful when the server address is registered as127.0.0.1or when you're 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-localauthis specified, in which case the default is/etc/openafs/server. this option allows the use of alternative configuration locations for testing purposes π§-helpβ prints the online help for this command. all other valid options are ignored. it's the "not me ignoring everything else" of flags π
π¦ OUTPUT π¦
if the command succeeds, vos rename produces no output. silence. iconic. queen behavior π
but if the volume named by the -oldname argument does not exist, you get this little message:
vos: Could not find entry for volume <old volume name>.
π EXAMPLES π
so here's a real one β someone had a mistaken volume name "sun4x_56.afsws" and needed it changed to the correct alternative "sun4x_56.usr.afsws". and the fix? one line, no cap:
% vos rename -oldname sun4x_56.afsws -newname sun4x_56.usr.afsws
ate. periodt π
π 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, the issuer must instead be logged on to a server machine as the local superuser "root". yes, actual root. no shortcuts, bestie π€
π SEE ALSO π
πΈ COPYRIGHT πΈ
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, you're all caught up π«Ά this was the OpenAFS edition, dated 2026-07-27 β go rename something and slay β¨π
π¦ where this page comes from
- ubuntu stonking: openafs-client 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