vos_release - Updates read-only volumes to match the read/write source volume


vos release -id <volume name or ID> [-force] [-clone [<yes|no>]] [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]


The vos release command copies the contents of a read/write source volume to each read-only site (file server and partition) registered with the Location Service. Use the vos_addsite(1) command to define sites before issuing the vos release command. Each read-only replica has the same name as the read/write source with the addition of a .readonly extension.

The vos release command attempts to ensure that all copies of the volume's read-only version match each other and the contents of the read/write volume at the moment the command was issued. In cases where problems such as network or File Server outages prevent successful completion of the release operation, the administrator is notified by two methods.

First, the vos release command generates an error message on the standard error stream indicating each read-only site that did not receive the new volume version. Second, the volume's location information as reported by vos_examine(1) and vos_listloc(1) will label each read-only site with New release, Old release, or Not released.

The Cache Manager refuses to access a read-only site marked with the Old release flag, which potentially imposes a greater load on the sites marked with the New release flag. It is important to repair the failure and then re-issue the vos release command as many times as necessary to complete the release without errors.

The pattern of site flags remaining in the volume's location information after a failed release operation can help determine the point at which the operation failed. The steps of the vos release operation are as follows:

If the vos release operation does not successfully complete, one of the flags (New release, Old release, or Not released) will be present on the read-only sites and the ReleaseClone will not be deleted.

vos(1) uses the following rules to determine whether or not it must create a new ReleaseClone:


-id <volume name or id>

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


Specifies that vos release should create a new ReleaseClone and update all of the replica sites even if the read/write volume has not been modified.

-clone [<yes|no>]

The -clone option defaults to yes. When set to yes, vos release avoids taking replica sites offline by cloning both the source and destinations to temporary clones, applying updates, and then bringing all clones online as updated read-only volumes. When cloning is disabled, the volume data is copied from the source read/write volume and to the designated read-only volumes without temporary clones. This will result in the source and destination volumes being offline until the vos release has completed. vos release -clone no is faster because it doesn't create and delete temporary clones on each of the source and destination sites.

-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 command clones the read/write volume usr and releases it to the read-only sites listed with the Location Service.

   % vos release usr


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_addsite(1), vos_examine(1), vos_listloc(1)


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.