vos_syncloc - Verifies location information for volumes housed at a specified site
vos syncloc [-server <machine name>] [-partition <partition name>] [-volume <volume name or ID>] [-force] [-dryrun] [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]
The vos syncloc command verifies that the location information for all volumes housed either on all partitions on the File Server specified by the -server argument, or on the single partition specified by the -server and -partition arguments, is recorded correctly by the Location Service. The -volume argument can be used to restrict the operation to a single volume.
If the -volume argument is not included, the command interpreter obtains from the File Server a list of the volumes that reside on each partition, then updates the location information for each volume as necessary to reflect their state on the partition. For example, if the vos syncloc command finds a volume that is not known to the Location Service, it will attempt to add the volume to the Location Service. However, if the Location Service knows a different location for the volume, or there are irreconcilable conflicts, it instead writes a message about the conflict to the standard error stream. The command never removes volumes from File Servers.
To achieve complete volume location consistency, run this command on all File Servers in the cell, and then run the vos_syncfs(1) command on all File Servers in the cell.
Using the -volume argument basically combines the effects of this command with those of the vos_syncfs(1) command for a single volume. The command not only verifies that the Location Service has the correct information for the specified volume type (read/write, backup, or read-only), but also checks that any related volume types known to the Location Service actually exist at the specified sites. It is not necessary to provide the -server argument (and optionally, -partition argument); if one or both is provided, the results are reliable only if they specify the actual location of the volume indicated by the -volume argument.
Identifies the File Server housing the volumes for which location information will be verified. Provide a fully qualified host name, an IP address or UUID as reported by vos_listfs(1).
Identifies the partition housing the volumes for which to verify location information.
Provide the -server argument along with this one.
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).
Specifies the name or volume ID number of a single volume for which to verify the location information. This argument can be combined with the -server (and optionally, the -partition) argument.
If a File Server is unreachable, treat any partitions and volumes on them as if they do not exist. Use this switch when a File Server has failed or has been taken out of service without relocating the volumes.
Show the actions which would be taken, but do not make changes.
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.
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.
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 command verifies the location information for each volume stored on the File Server fs4.your-cell-name.com.
% vos syncloc fs4.your-cell-name.com
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.
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.
"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.