3 vos examine - Shows volume header and VLDB entry information for a volume
7 B<vos examine> B<-id> <I<volume name or ID>> [B<-extended>]
8 [B<-cell> <I<cell name>>] [B<-noauth>] [B<-localauth>] [B<-verbose>]
11 B<vos e> B<-i> <I<volume name or ID>> [B<-e>] [B<-c> <I<cell name>>]
12 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
14 B<vos volinfo> B<-i> <I<volume name or ID>> [B<-e>] [-c <I<cell name>>]
15 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
17 B<vos v> B<-i> <I<volume name or ID>> [B<-e>] [B<-c> <I<cell name>>]
18 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
22 The B<vos examine> command formats and displays information from the
23 Volume Location Database (VLDB) entry and the volume header of the volume
24 specified by the B<-id> argument.
26 To display the volume header only, use the B<vos listvol> command. To
27 display information from the VLDB only, use the B<vos listvldb> command.
33 =item B<-id> <I<volume name or ID>>
35 Specifies either the complete name or volume ID number of the volume,
36 which can be read/write, read-only, or backup.
40 Display statistics about read and write operations on files and
41 directories in the volume.
43 =item B<-cell> <I<cell name>>
45 Names the cell in which to run the command. Do not combine this argument
46 with the B<-localauth> flag. For more details, see L<vos(1)>.
50 Assigns the unprivileged identity C<anonymous> to the issuer. Do not
51 combine this flag with the B<-localauth> flag. For more details, see
56 Constructs a server ticket using a key from the local
57 F</usr/afs/etc/KeyFile> file. The B<vos> command interpreter presents it
58 to the Volume Server and Volume Location Server during mutual
59 authentication. Do not combine this flag with the B<-cell> argument or
60 B<-noauth> flag. For more details, see L<vos(1)>.
64 Produces on the standard output stream a detailed trace of the command's
65 execution. If this argument is omitted, only warnings and error messages
70 Prints the online help for this command. All other valid options are
77 The first seven lines of the output show information from the volume
78 header and the remaining lines come from the VLDB. Each item in the
79 following list corresponds to a line of output derived from the volume
86 Basic information about the specified volume (displayed on a single
101 Type (the flag is C<RW> for read/write, C<RO> for read-only, C<BK> for
106 Size in kilobytes (C<1024> equals a megabyte)
110 Number of files in the volume, if the B<-extended> flag is provided
114 Status on the file server machine, which is one of the following:
120 The volume is completely accessible to Cache Managers.
124 The volume is not accessible to Cache Managers, but does not seem to be
125 corrupted. This status appears while a volume is being dumped, for
128 =item Off-line**needs salvage**
130 The volume is not accessible to Cache Managers, because it seems to be
131 corrupted. Use the B<bos salvage> or B<salvager> command to repair the
140 The file server machine and partition that house the volume, as determined
141 by the command interpreter as the command runs, rather than derived from
142 the VLDB or the volume header.
146 The volume ID numbers associated with the various versions of the volume:
147 read/write (C<RWrite>), read-only (C<ROnly>), backup (C<Backup>), and
148 ReleaseClone (C<RClone>). One of them matches the volume ID number that
149 appears on the first line of the volume's output. If the value in the
150 C<RWrite>, C<ROnly>, or C<Backup> field is C<0> (zero), there is no volume
151 of that type. If there is currently no ReleaseClone, the C<RClone> field
152 does not appear at all.
156 The maximum space quota allotted to the read/write copy of the volume,
157 expressed in kilobyte blocks in the C<MaxQuota> field.
161 The date and time the volume was created, in the C<Creation> field. If the
162 volume has been restored with the B<backup diskrestore>, B<backup
163 volrestore>, or B<vos restore> command, this is the restore time.
167 The date and time when the contents of the volume last changed, in the
168 C<Last Update> field. For read-only and backup volumes, it matches the
169 timestamp in the C<Creation> field.
173 The number of times the volume has been accessed for a fetch or store
174 operation since the later of the two following times:
180 12:00 a.m. on the day the command is issued
184 The last time the volume changed location
190 When the B<-extended> flag is included, two tables appear next:
196 The table labeled C<Raw Read/Write Stats> contains information on the
197 number of reads (fetches) and writes (stores) made on the specified
202 The table labeled C<Writes Affecting Authorship> contains information on
203 writes made to files and directories in the specified volume.
207 If the following message appears instead of the previously listed
208 information, it indicates that a volume is not accessible to Cache
209 Managers or the B<vos> command interpreter, for example because a clone is
212 **** Volume <volume_ID> is busy ****
214 If the following message appears instead of the previously listed
215 information, it indicates that the File Server is unable to attach the
216 volume, perhaps because it is seriously corrupted. The F<FileLog> and
217 F<VolserLog> log files in the F</usr/afs/logs> directory on the file
218 server machine possibly provide additional information; use the B<bos
219 getlog> command to display them.
221 **** Could not attach volume <volume_ID> ****
223 Following a blank line, information from the VLDB entry appears. Each
224 item in this list corresponds to a separate line in the output:
230 The base (read/write) volume name. The read-only and backup versions have
231 the same name with a C<.readonly> and C<.backup> extension, respectively.
235 The volume ID numbers allocated to the versions of the volume that
236 actually exist, in fields labeled C<RWrite> for the read/write, C<ROnly>
237 for the read-only, C<Backup> for the backup, and C<RClone> for the
238 ReleaseClone. (If a field does not appear, the corresponding version of
239 the volume does not exist.) The appearance of the C<RClone> field normally
240 indicates that a release operation did not complete successfully; the
241 C<Old release> and C<New release> flags often also appear on one or more
242 of the site definition lines described just following.
246 The number of sites that house a read/write or read-only copy of the
247 volume, following the string C<< number of sites -> >>.
251 A line for each site that houses a read/write or read-only copy of the
252 volume, specifying the file server machine, partition, and type of volume
253 (C<RW> for read/write or C<RO> for read-only). If a backup version exists,
254 it is understood to share the read/write site. Several flags can appear
255 with a site definition:
261 Indicates that the vos release command has not been issued since the B<vos
262 addsite> command was used to define the read-only site.
266 Indicates that a vos release command did not complete successfully,
267 leaving the previous, obsolete version of the volume at this site.
271 Indicates that a vos release command did not complete successfully, but
272 that this site did receive the correct new version of the volume.
278 If the VLDB entry is locked, the string C<Volume is currently LOCKED>.
282 For further discussion of the C<New release> and C<Old release> flags, see
287 The following example shows output for the ABC Corporation volume called
288 C<usr> with two read-only replication sites (this volume is mounted at the
289 F</afs/abc.com/usr> directory). For the sake of illustration, the output
290 shows the volume as locked.
293 usr 536870981 RW 3459 K On-line
295 RWrite 5360870981 ROnly 536870982 Backup 536870983
297 Creation Mon Jun 12 15:22:06 1989
298 Last Update Fri Jun 16 09:34:35 1989
299 5719 accesses in the past day (i.e., vnode references)
300 RWrite: 5360870981 ROnly: 536870982 Backup: 536870983
302 server fs1.abc.com partition /vicepa RO Site
303 server fs3.abc.com partition /vicepa RO Site
304 server fs2.abc.com partition /vicepb RW Site
305 Volume is currently LOCKED
307 The following example shows the output for the volume C<user.terry> using
308 the B<-extended> flag. The volume has no read-only replication sites.
310 % vos examine -id user.terry -extended
311 user.terry 354287190 RW 2302 K used 119 files On-line
313 RWrite 354287190 ROnly 0 Backup 354287192
315 Creation Wed Nov 25 17:38:57 1992
316 Last Update Tue Dec 15 10:46:20 1992
317 598 accesses in the past day (i.e., vnode references)
319 |-------------------------------------------|
320 | Same Network | Diff Network |
321 |----------|----------|----------|----------|
322 | Total | Auth | Total | Auth |
323 |----------|----------|----------|----------|
324 Reads | 55 | 55 | 38 | 38 |
325 Writes | 95 | 95 | 0 | 0 |
326 |-------------------------------------------|
327 Writes Affecting Authorship
328 |-------------------------------------------|
329 | File Authorship | Directory Authorship|
330 |----------|----------|----------|----------|
331 | Same | Diff | Same | Diff |
332 |----------|----------|----------|----------|
333 0-60 sec | 38 | 0 | 21 | 1 |
334 1-10 min | 2 | 0 | 7 | 0 |
335 10min-1hr | 0 | 0 | 1 | 0 |
336 1hr-1day | 1 | 0 | 5 | 1 |
337 1day-1wk | 0 | 0 | 0 | 0 |
338 > 1wk | 0 | 0 | 0 | 0 |
339 |-------------------------------------------|
340 RWrite: 354287190 Backup: 354287192
342 server fs4.abc.com partition /vicepc RW Site
344 =head1 PRIVILEGE REQUIRED
350 L<backup_diskrestore(8)>,
351 L<backup_volrestore(8)>,
363 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
365 This documentation is covered by the IBM Public License Version 1.0. It was
366 converted from HTML to POD by software written by Chas Williams and Russ
367 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.