vos_status - Reports a Volume Server's transaction status
vos status -server <machine name> -id <volume group id> [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]
The vos status command displays the list of in-progress transactions (if any). If there are no active transactions, the following message appears:
No active transactions on <machine_name>
This command is useful mainly if there is concern that the File Server is not performing requested actions.
Identifies the File Server for which to display status information. Provide a fully qualified host name, an IP address or UUID as reported by vos_listfs(1).
Restrict the volserver status query to transactions involving members of the volume group specified.
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.
There are two possible types of output.
The following message indicates that the Volume Server is not currently performing any actions.
No active transactions on I<machine name>
The other possible output is information describing the number of and state of active Volume Server transactions. For each transaction the following fields are displayed:
transaction, the unique transaction identifier
created, the time at which this transaction started
lastActiveTime, the time when transaction data was most recently received or sent
returnCode, if present, the transaction when it completes will fail with the specified error code
attachFlags, if present, the mode with which the volume was attached to the transaction. Possible values are offline and busy
volumeStatus, if present, can include:
deleteOnSalvage, indicates that the volume will be deleted if the transaction fails or is interrupted.
outOfService, the volume will be left in an offline state when the transaction fails or is interrupted.
deleted, the volume will be deleted at the end of the transaction.
transactionFlags, if present, indicates the transaction has completed and is awaiting garbage collection by the Volume Server.
volume, which specifies the affected volume's ID number
group, if present, indicates the volume ID of the associated RW volume
partition, indicates where the affected volume resided at the start of the transaction
procedure, indicates the internal subprocedure being executed
calls, indicates the number of active remote procedure calls associated with this transaction
Many volume transactions involve the execution of one or more remote procedure calls. For each call the following details are reported:
endpoint, when reported by the Volume Server, the IP address and port number of the peer remote procedure call service.
dataRead, when reported by the Volume Server, the number of data bytes received by the Volume Server so far.
lastReceiveTime, the time the last byte of data was received by the Volume Server.
dataSent, when reported by the Volume Server, the number of data bytes sent by the Volume Server so far.
lastSendTime, the time the last byte of data was sent by the Volume Server.
The endpoint, dataRead and dataSent fields are unavailable when the Volume Server is IBM AFS or OpenAFS.
The following example illustrates the kind of output that sometimes appears when the File Server fs1.your-cell-name.com is executing a dump at the time this command is issued.
% vos status fs1.your-cell-name.com
--------------------------------------------
transaction: 575 created: Tue Jan 2 8:34:56 1990 lastActiveTime: Tue Jan 2 8:36:36 1990
attachFlags: offline
volume: 536871080 group: 536871080 partition: /vicepb procedure: Dump
calls: 1
1. from 192.168.10.10:3827
dataRead: 1609 lastReceiveTime: Tue Jan 2 8:34:57 1990
dataSent: Tue Jan 2 8:34:56 1990 lastSendTime: Tue Jan 2 8:36:36 1990
error: 0
--------------------------------------------
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.