vos_addsite - Adds a read-only site definition to a volume's VLDB entry


vos addsite -server <machine name for new site> -partition <partition name for new site> -id <volume name or ID> [-roid <readonly volume ID>] [-valid] [-force] [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]


The vos addsite command registers with the Location Service a new read-only site for the read/write volume named by the -id argument. The site is specified by the -server and -partition arguments. When the vos release command is next issued against the read/write volume, a read-only snapshot of it will be distributed to all of the read-only sites including the newly registered one.


The Volume Service will register a maximum of 13 read-only sites per read/write volume.


-server <hostname, IP address or UUID>

Identifies the File Server where the read-only volume is to reside. Provide a fully qualified host name, an IP address or UUID as reported by vos_listfs(1).

-partition <partition name>

Identifies the partition on the File Server named by the -server argument where the read-only volume is to reside. Provide the partition's complete name with preceding slash (for example, /vicepa) or use one of the three acceptable abbreviated forms. For details, see vos(1).

-id <volume name or ID>

Specifies either the name or ID number of the read/write volume.

-roid <readonly volume ID>

Specifies the ID number of the readonly volume. This will only be honored if the read/write volume does not already have a readonly volume ID associated with it. If the read/write volume already has a readonly volume ID, the specified ID will be ignored, and a warning will be printed.

If this is not specified and the read/write volume does not already have a readonly volume ID, a volume ID will be allocated for the readonly volume when the vos_release(1) command is run.

Cell administrators should never need to specify a readonly volume ID.


Instructs the Location Service that the readonly volume located at the site specified by -server and -partition is up-to-date. Cell administrators should only do this if the new site already has a current readonly replica of the read/write volume that has not previously been registered with the Location Service. -valid should be used after an existing readonly volume is dumped with vos_dump(1) and restored with vos_restore(1) -readonly to the new site.


Permits the registration of a readonly site to the Location Service when the specified server is unreachable, or when the specified partition is not attached.

-cell <cell name>

Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1).


Assigns the unprivileged identity anonymous to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1).


Obtains an authentication token using the server encryption key with the highest key version number in the local /etc/yfs/server/KeyFileExt file. The resulting token never expires and has Super User privileges. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1).


Use the calling user's tokens from the kernel or as obtained using the active Kerberos ticket granting ticket to communicate with the Volume Server and Location Service. This is the default if neither -localauth nor -noauth is given.

Since this option is the default, it is usually not useful for running single command line operations. However, it can be useful when running commands via vos_interactive(1) or vos_source(1), since otherwise it would be impossible to switch from, for example, -localauth back to using regular tokens during a bulk operation.


Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear.

-encrypt [<yes|no>]

Enables or disables encrytion for the command so that the operation's results are not transmitted across the network in clear text.


Shows all servers as IP addresses instead of the reverse DNS lookup hostname. -noresolve useful when troubleshooting no such volume and volume moved errors.

-config <configuration file>

Set the location of the configuration file to be used. The default file is /etc/yfs/yfs-client.conf.


Prints the online help for this command. All other valid options are ignored.


The following example registers a readonly site for the cell's root.cell volume.

   % vos addsite -server -partition /vicep1 -id root.cell


The issuer must be listed in the /etc/yfs/server/UserListExt file on the File Server specified by the -server argument and on each Location Server. If the -localauth flag is included, the issuer must instead be logged on to a server with an account capable of reading the /etc/yfs/server/KeyFileExt file.


vos(1), vos_dump(1), vos_examine(1), vos_release(1), KeyFileExt(5), UserListExt(5)


IBM Corporation 2000. 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.


"AFS" is a registered mark of International Business Machines Corporation, used under license. (USPTO Registration 1598389)

"OpenAFS" is a registered mark of International Business Machines Corporation. (USPTO Registration 4577045)

The "AuriStor" name, log 'S' brand mark, and icon are registered marks of AuriStor, Inc. (USPTO Registrations 4849419, 4849421, and 4928460) (EUIPO Registration 015539653).

"Your File System" is a registered mark of AuriStor, Inc. (USPTO Registrations 4801402 and 4849418).

"YFS" and "AuriStor File System" are trademarks of AuriStor, Inc.