Langue: en

Autres versions - même langue

Version: 174935 (fedora - 06/07/09)

Section: 8 (Commandes administrateur)


volutil - volume utility subsystem


volutil [-h <server>] [ -t timeout] [ -d debuglevel] <command> <parameters ... >


Volutil is a RPC interface to the volume utility subsystem of the file server. The volume utilities are used to perform administrative functions like creating, cloning, purging, dumping and restoring volumes. Each of these functions can be invoked via the <command> parameter. Each command has a set of parameters that it expects. These are listed below along with a short description of each command. The volutil utility may be instructed to perform the operations on a server at a remote site by specifying the server to which to connect with the -h option. The default is to connect to a server on the local machine. The -t option may be used to specify the timeout (in seconds) to be used by RPC2.

ancient <group-ID> <rep-ID>
.IP • .IP n(el. Tell the server that backup succeeded for this volume. The next dump of this volume, if incremental, will be based on the state represented by this backup. The input should be in Hex.
backup <volume-ID>
.IP • .IP n(el. Create a backup clone of a read/write volume. If a backup clone already exists, update it to reflect the current state of the read/write volume; Otherwise, create a new read-only volume. The read/write volume must be locked for this to succeed. Backup unlocks the volume as a side effect.
clone volume-ID [-n new-volume-name]
.IP • .IP n(el. Create a read only clone of a read write volume with (replica) ID (<volume-ID>). The vnodes are actually copied but the inodes are marked copy-on-write i.e. inodes need to be copied only if modified. The name of the new cloned volume can be optionally specified by the <new-volume-name> parameter. Default value is volume-name.readonly. The clone(8) command can be used to call volutil clone.
create <partition-path> <volume-name>
.IP • .IP n(el. Create a nonreplicated read-write volume named <volume-name> on partition named <partition-path>. The createvol(8) command is a simplified front-end for this option.
create_rep <partition-path>
<volume-name> <group-ID>" .IP • .IP n(el. Create a replicated read-write volume named <volume-name> on partition named <partition-path>. The <group-ID> parameter is used to specify the ID of the replicated volume to which this replica will belong. The createvol_rep(8) command will also create a replicated volume.
dump [-i] <volume-ID>
<file-name>" .IP • .IP n(el. Dump the entire contents of a volume (volume-ID in Hex) to a file (file-name). If the -i flag is used, the dump will be incremental, it will only include vnodes which have been modified since the last dump was taken. The dump is not machine independent, certain fields in the Vnode are not translated to network order. However, dump files can be used to create restored volumes on machines with a similar byte-order.
dumpmem <file-name> <address> <size>
.IP • .IP n(el. Dump <size> bytes starting at <address> into <file-name>.
elapse <on | off> <resolution | cb | mond | volDump> [MultiRPC]
.IP • .IP n(el. Turn on or off timers for the given subsystem.
info [-all] <volume-name |
volume-number> <file-name>" .IP • .IP n(el. Print in ascii the contents of a volume into a file (<file-name>). The volume can be specified by its name, or by the volume-ID, specified in Hex. If -all is specified, contents of both large and small vnodes in that volume are also printed.
lock <volume-ID>
.IP • .IP n(el. Lock a volume to prevent write access to the volume. To other users it will appear as if the operation would time out.
lookup <volume-name | volume-ID>
<file-name>" .IP • .IP n(el. Print information about a volume (specified by volume-name or volume-ID specified in Hex) in file-name. Only meta-information, such as replicated group-ID, location, etc. is printed.
makevldb <VolumeList>
.IP • .IP n(el. Create a new Volume Location Database VLDB. VolumeList names a file containing volume parameters for all volumes in the system. This command typically is run on the system control machine. See also bldvldb(8) and volumelist(5).
makevrdb <vrlist>
.IP • .IP n(el. Create a new Volume Replication Data Base (VRDB). <vrlist> is a file containing entries describing replicated volumes. Each entry contains the name, group-ID, read-write ids, and the VSG address of a replicated volume. There is one entry per replicated volume in the system.
purge <volume-ID> <volume-name>
.IP • .IP n(el. Delete a volume. For replicated volumes purge must be called from each server individually on the replicas at the different servers. (See purgevol-rep(8))
restore <file-name>
<partition-path> [<volume-name> [<volume-ID> ] ]" .IP • .IP n(el. Create a new volume on the partition named by <partition-path> and read in the contents from a dump in file <file-name>. The new volume will be given the name and ID specified on the command line. If either is unspecified, or if the Volume ID is of illegal form, the server will allocate the ID or name based on internal rules. The volume-ID should be specified in Hex.
rvmsize <volume-ID>
.IP • .IP n(el. Print the RVM statistics for the volume <volume-ID>.
setdebug <level>
.IP • .IP n(el. Set the debug level for the volume and directory packages to level. To reset it use zero for the level argument. The rpc2 debug level is set to level/10.
setlogparms <volume-ID>
[reson <4 | 0>] [logsize <size>]" .IP • .IP n(el. Turn on resolution or change the log size for a volume. The volume ID can be either the replicated ID or the non-replicated ID. Resolution is turned on by specifying 4 after reson and can be turned off by specifying 0. The size of the log can also be changed for the volume. The size parameter refers to the number of maximum entries in the log. This should be a multiple of 32. Typically this is set to 8192.

NOTE: You should in all normal cases keep the resolution turned on, and the argument for reson is in that case 4!

setvv <volumeNumber> <vnodeNumber>
<Uniquifier> <version numbers (8)> <host unique flags>" .IP • .IP n(el. Set the version vector for a vnode (with fid = <volumeNumber>.<vnodeNumber>.<Uniquifier>). The new version vector is specified by the <version numbers> and the <host unique flags> triple.
showvnode <volumeNumber>
<vnodeNumber> <Uniquifier> <file-name>" .IP • .IP n(el. Print the contents of a vnode (with fid = <volumeNumber>.<vnodeNumber>.<Uniquifier>). into <file-name>.
.IP • .IP n(el. Bring all volumes offline and bring down the server.
.IP • .IP n(el. Save the fileserver log output (in SrvLog.old) and start a new SrvLog.
timing on | off <filename>
.IP • .IP n(el. Turn timing on or off.
.IP • .IP n(el. Forcibly truncate the RVM log.
unlock <volume-ID>
.IP • .IP n(el. Unlock a volume locked via the volutil lock command. (volume-ID) should be in Hex
.IP • .IP n(el. Make the file server read in a new VLDB and VRDB. The server assumes the databases to exist in /vice/db/VLDB and /vice/db/VRDB. This utility is useful for reading in new databases at non-scm machines.


This command must be run as root. It works only on the machine running the server. Also, the token file /vice/db/voutil.tk must be accessible.


The salvage option to volutil doesn't work right. Please don't try it.








vrdb(5), volumelist(5), bldvldb(8), createvol(8), createvol_rep(8), purgevol(8), purgevol_rep(8)


Puneet Kumar, David Steere, 1990, Created