1volutil(8) System Manager's Manual volutil(8)
2
6 volutil - volume utility subsystem
7
10 volutil [-h <server>] [ -t timeout] [ -d debuglevel] <command> <parame‐
11 ters ... >
12
14 Volutil is a RPC interface to the volume utility subsystem of the file
15 server. The volume utilities are used to perform administrative func‐
16 tions like creating, cloning, purging, dumping and restoring volumes.
17 Each of these functions can be invoked via the <command> parameter.
18 Each command has a set of parameters that it expects. These are listed
19 below along with a short description of each command. The volutil
20 utility may be instructed to perform the operations on a server at a
21 remote site by specifying the server to which to connect with the -h
22 option. The default is to connect to a server on the local machine.
23 The -t option may be used to specify the timeout (in seconds) to be
24 used by RPC2.
25 ancient <group-ID> <rep-ID>
27 Tell the server that backup succeeded for this volume. The next
28 dump of this volume, if incremental, will be based on the state
29 represented by this backup. The input should be in Hex.
30 backup <volume-ID>
33 Create a backup clone of a read/write volume. If a backup clone
34 already exists, update it to reflect the current state of the
35 read/write volume; Otherwise, create a new read-only volume.
36 The read/write volume must be locked for this to succeed.
37 Backup unlocks the volume as a side effect.
38 clone volume-ID [-n new-volume-name]
41 Create a read only clone of a read write volume with (replica)
42 ID (<volume-ID>). The vnodes are actually copied but the inodes
43 are marked copy-on-write i.e. inodes need to be copied only if
44 modified. The name of the new cloned volume can be optionally
45 specified by the <new-volume-name> parameter. Default value is
46 volume-name.readonly. The clone(8) command can be used to call
47 volutil clone.
48 create <partition-path> <volume-name>
52 Create a nonreplicated read-write volume named <volume-name> on
53 partition named <partition-path>. The createvol(8) command is a
54 simplified front-end for this option.
55 create_rep <partition-path>
59 <volume-name> <group-ID>" Create a replicated read-write volume
60 named <volume-name> on partition named <partition-path>. The
61 <group-ID> parameter is used to specify the ID of the replicated
62 volume to which this replica will belong. The createvol_rep(8)
63 command will also create a replicated volume.
64 dump [-i] <volume-ID>
68 <file-name>" Dump the entire contents of a volume (volume-ID in
69 Hex) to a file (file-name). If the -i flag is used, the dump
70 will be incremental, it will only include vnodes which have been
71 modified since the last dump was taken. The dump is not machine
72 independent, certain fields in the Vnode are not translated to
73 network order. However, dump files can be used to create
74 restored volumes on machines with a similar byte-order.
75 dumpmem <file-name> <address> <size>
78 Dump <size> bytes starting at <address> into <file-name>.
79 elapse <on │ off> <resolution │ cb │ mond │ volDump> [MultiRPC]
82 Turn on or off timers for the given subsystem.
83 info [-all] <volume-name │
86 volume-number> <file-name>" Print in ascii the contents of a
87 volume into a file (<file-name>). The volume can be specified by
88 its name, or by the volume-ID, specified in Hex. If -all is
89 specified, contents of both large and small vnodes in that vol‐
90 ume are also printed.
91 lock <volume-ID>
94 Lock a volume to prevent write access to the volume. To other
95 users it will appear as if the operation would time out.
96 lookup <volume-name │ volume-ID>
99 <file-name>" Print information about a volume (specified by vol‐
100 ume-name or volume-ID specified in Hex) in file-name. Only
101 meta-information, such as replicated group-ID, location, etc. is
102 printed.
103 makevldb <VolumeList>
106 Create a new Volume Location Database VLDB. VolumeList names a
107 file containing volume parameters for all volumes in the system.
108 This command typically is run on the system control machine.
109 See also bldvldb(8) and volumelist(5).
110 makevrdb <vrlist>
113 Create a new Volume Replication Data Base (VRDB). <vrlist> is a
114 file containing entries describing replicated volumes. Each
115 entry contains the name, group-ID, read-write ids, and the VSG
116 address of a replicated volume. There is one entry per repli‐
117 cated volume in the system.
118 purge <volume-ID> <volume-name>
121 Delete a volume. For replicated volumes purge must be called
122 from each server individually on the replicas at the different
123 servers. (See purgevol-rep(8))
124 restore <file-name>
127 <partition-path> [<volume-name> [<volume-ID> ] ]" Create a new
128 volume on the partition named by <partition-path> and read in
129 the contents from a dump in file <file-name>. The new volume
130 will be given the name and ID specified on the command line. If
131 either is unspecified, or if the Volume ID is of illegal form,
132 the server will allocate the ID or name based on internal rules.
133 The volume-ID should be specified in Hex.
134 rvmsize <volume-ID>
137 Print the RVM statistics for the volume <volume-ID>.
138 setdebug <level>
141 Set the debug level for the volume and directory packages to
142 level. To reset it use zero for the level argument. The rpc2
143 debug level is set to level/10.
144 setlogparms <volume-ID>
147 [reson <4 │ 0>] [logsize <size>]" Turn on resolution or change
148 the log size for a volume. The volume ID can be either the
149 replicated ID or the non-replicated ID. Resolution is turned on
150 by specifying 4 after reson and can be turned off by specifying
151 0. The size of the log can also be changed for the volume. The
152 size parameter refers to the number of maximum entries in the
153 log. This should be a multiple of 32. Typically this is set to
154 8192.
155 NOTE: You should in all normal cases keep the resolution turned
157 on, and the argument for reson is in that case 4!
158 setvv <volumeNumber> <vnodeNumber>
161 <Uniquifier> <version numbers [4m(8)> <host unique flags>" Set the
162 version vector for a vnode (with fid = <volumeNumber>.<vnodeNum‐
163 ber>.<Uniquifier>). The new version vector is specified by the
164 <version numbers> and the <host unique flags> triple.
165 showvnode <volumeNumber>
168 <vnodeNumber> <Uniquifier> <file-name>" Print the contents of a
169 vnode (with fid = <volumeNumber>.<vnodeNumber>.<Uniquifier>).
170 into <file-name>.
171 shutdown
175 Bring all volumes offline and bring down the server.
176 swaplog
179 Save the fileserver log output (in SrvLog.old) and start a new
180 SrvLog.
181 timing on │ off <filename>
184 Turn timing on or off.
185 truncatervmlog
188 Forcibly truncate the RVM log.
189 unlock <volume-ID>
192 Unlock a volume locked via the volutil lock command. (volume-ID)
193 should be in Hex
194 updatedb
197 Make the file server read in a new VLDB and VRDB. The server
198 assumes the databases to exist in /vice/db/VLDB and
199 /vice/db/VRDB. This utility is useful for reading in new data‐
200 bases at non-scm machines.
201
204 This command must be run as root. It works only on the machine running
205 the server. Also, the token file /vice/db/voutil.tk must be accessible.
206
208 The salvage option to volutil doesn't work right. Please don't try it.
209
211 /vice/db/VSGDB
212 /vice/file/SrvLog
214 /vice/db/VLDB
216 /vice/db/VRDB
218 /vice/vol/VRList
220
222 vrdb(5), volumelist(5), bldvldb(8), createvol(8), createvol_rep(8),
223 purgevol(8), purgevol_rep(8)
224
226 Puneet Kumar, David Steere, 1990, Created
227 volutil(8)