3 vos_examine - Shows volume header and VLDB entry information for a volume
10 B<vos examine> S<<< B<-id> <I<volume name or ID>> >>> [B<-extended>]
11 S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>] [B<-verbose>]
14 B<vos e> S<<< B<-i> <I<volume name or ID>> >>> [B<-e>] S<<< [B<-c> <I<cell name>>] >>>
15 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
17 B<vos volinfo> S<<< B<-i> <I<volume name or ID>> >>> [B<-e>] [-c <I<cell name>>]
18 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
20 B<vos v> S<<< B<-i> <I<volume name or ID>> >>> [B<-e>] S<<< [B<-c> <I<cell name>>] >>>
21 [B<-n>] [B<-l>] [B<-v>] [B<-h>]
28 The B<vos examine> command formats and displays information from the
29 Volume Location Database (VLDB) entry and the volume header of the volume
30 specified by the B<-id> argument.
32 To display the volume header only, use the B<vos listvol> command. To
33 display information from the VLDB only, use the B<vos listvldb> command.
37 Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
43 =item B<-id> <I<volume name or ID>>
45 Specifies either the complete name or volume ID number of the volume,
46 which can be read/write, read-only, or backup.
50 Display statistics about read and write operations on files and
51 directories in the volume.
53 =item B<-cell> <I<cell name>>
55 Names the cell in which to run the command. Do not combine this argument
56 with the B<-localauth> flag. For more details, see L<vos(1)>.
60 Assigns the unprivileged identity C<anonymous> to the issuer. Do not
61 combine this flag with the B<-localauth> flag. For more details, see
66 Constructs a server ticket using a key from the local
67 F</usr/afs/etc/KeyFile> file. The B<vos> command interpreter presents it
68 to the Volume Server and Volume Location Server during mutual
69 authentication. Do not combine this flag with the B<-cell> argument or
70 B<-noauth> flag. For more details, see L<vos(1)>.
74 Produces on the standard output stream a detailed trace of the command's
75 execution. If this argument is omitted, only warnings and error messages
80 Prints the online help for this command. All other valid options are
87 The first seven lines of the output show information from the volume
88 header and the remaining lines come from the VLDB. Each item in the
89 following list corresponds to a line of output derived from the volume
96 Basic information about the specified volume (displayed on a single
111 Type (the flag is C<RW> for read/write, C<RO> for read-only, C<BK> for
116 Size in kilobytes (C<1024> equals a megabyte)
120 Number of files in the volume, if the B<-extended> flag is provided
124 Status on the file server machine, which is one of the following:
130 The volume is completely accessible to Cache Managers.
134 The volume is not accessible to Cache Managers, but does not seem to be
135 corrupted. This status appears while a volume is being dumped, for
138 =item Off-line**needs salvage**
140 The volume is not accessible to Cache Managers, because it seems to be
141 corrupted. Use the B<bos salvage> or B<salvager> command to repair the
150 The file server machine and partition that house the volume, as determined
151 by the command interpreter as the command runs, rather than derived from
152 the VLDB or the volume header.
156 The volume ID numbers associated with the various versions of the volume:
157 read/write (C<RWrite>), read-only (C<ROnly>), backup (C<Backup>), and
158 ReleaseClone (C<RClone>). One of them matches the volume ID number that
159 appears on the first line of the volume's output. If the value in the
160 C<RWrite>, C<ROnly>, or C<Backup> field is C<0> (zero), there is no volume
161 of that type. If there is currently no ReleaseClone, the C<RClone> field
162 does not appear at all.
166 The maximum space quota allotted to the read/write copy of the volume,
167 expressed in kilobyte blocks in the C<MaxQuota> field.
171 The date and time the volume was created, in the C<Creation> field. If the
172 volume has been restored with the B<backup diskrestore>, B<backup
173 volrestore>, or B<vos restore> command, this is the restore time.
177 The date and time when the contents of the volume last changed, in the
178 C<Last Update> field. For read-only and backup volumes, it matches the
179 timestamp in the C<Creation> field.
183 The number of times the volume has been accessed for a fetch or store
184 operation since the later of the two following times:
190 12:00 a.m. on the day the command is issued
194 The last time the volume changed location
200 When the B<-extended> flag is included, two tables appear next:
206 The table labeled C<Raw Read/Write Stats> contains information on the
207 number of reads (fetches) and writes (stores) made on the specified
212 The table labeled C<Writes Affecting Authorship> contains information on
213 writes made to files and directories in the specified volume.
217 If the following message appears instead of the previously listed
218 information, it indicates that a volume is not accessible to Cache
219 Managers or the B<vos> command interpreter, for example because a clone is
222 **** Volume <volume_ID> is busy ****
224 If the following message appears instead of the previously listed
225 information, it indicates that the File Server is unable to attach the
226 volume, perhaps because it is seriously corrupted. The F<FileLog> and
227 F<VolserLog> log files in the F</usr/afs/logs> directory on the file
228 server machine possibly provide additional information; use the B<bos
229 getlog> command to display them.
231 **** Could not attach volume <volume_ID> ****
233 Following a blank line, information from the VLDB entry appears. Each
234 item in this list corresponds to a separate line in the output:
240 The base (read/write) volume name. The read-only and backup versions have
241 the same name with a C<.readonly> and C<.backup> extension, respectively.
245 The volume ID numbers allocated to the versions of the volume that
246 actually exist, in fields labeled C<RWrite> for the read/write, C<ROnly>
247 for the read-only, C<Backup> for the backup, and C<RClone> for the
248 ReleaseClone. (If a field does not appear, the corresponding version of
249 the volume does not exist.) The appearance of the C<RClone> field normally
250 indicates that a release operation did not complete successfully; the
251 C<Old release> and C<New release> flags often also appear on one or more
252 of the site definition lines described just following.
256 The number of sites that house a read/write or read-only copy of the
257 volume, following the string C<< number of sites -> >>.
261 A line for each site that houses a read/write or read-only copy of the
262 volume, specifying the file server machine, partition, and type of volume
263 (C<RW> for read/write or C<RO> for read-only). If a backup version exists,
264 it is understood to share the read/write site. Several flags can appear
265 with a site definition:
271 Indicates that the vos release command has not been issued since the B<vos
272 addsite> command was used to define the read-only site.
276 Indicates that a vos release command did not complete successfully,
277 leaving the previous, obsolete version of the volume at this site.
281 Indicates that a vos release command did not complete successfully, but
282 that this site did receive the correct new version of the volume.
288 If the VLDB entry is locked, the string C<Volume is currently LOCKED>.
292 For further discussion of the C<New release> and C<Old release> flags, see
297 The following example shows output for the ABC Corporation volume called
298 C<usr> with two read-only replication sites (this volume is mounted at the
299 F</afs/abc.com/usr> directory). For the sake of illustration, the output
300 shows the volume as locked.
303 usr 536870981 RW 3459 K On-line
305 RWrite 5360870981 ROnly 536870982 Backup 536870983
307 Creation Mon Jun 12 15:22:06 1989
308 Last Update Fri Jun 16 09:34:35 1989
309 5719 accesses in the past day (i.e., vnode references)
310 RWrite: 5360870981 ROnly: 536870982 Backup: 536870983
312 server fs1.abc.com partition /vicepa RO Site
313 server fs3.abc.com partition /vicepa RO Site
314 server fs2.abc.com partition /vicepb RW Site
315 Volume is currently LOCKED
317 The following example shows the output for the volume C<user.terry> using
318 the B<-extended> flag. The volume has no read-only replication sites.
320 % vos examine -id user.terry -extended
321 user.terry 354287190 RW 2302 K used 119 files On-line
323 RWrite 354287190 ROnly 0 Backup 354287192
325 Creation Wed Nov 25 17:38:57 1992
326 Last Update Tue Dec 15 10:46:20 1992
327 598 accesses in the past day (i.e., vnode references)
329 |-------------------------------------------|
330 | Same Network | Diff Network |
331 |----------|----------|----------|----------|
332 | Total | Auth | Total | Auth |
333 |----------|----------|----------|----------|
334 Reads | 55 | 55 | 38 | 38 |
335 Writes | 95 | 95 | 0 | 0 |
336 |-------------------------------------------|
337 Writes Affecting Authorship
338 |-------------------------------------------|
339 | File Authorship | Directory Authorship|
340 |----------|----------|----------|----------|
341 | Same | Diff | Same | Diff |
342 |----------|----------|----------|----------|
343 0-60 sec | 38 | 0 | 21 | 1 |
344 1-10 min | 2 | 0 | 7 | 0 |
345 10min-1hr | 0 | 0 | 1 | 0 |
346 1hr-1day | 1 | 0 | 5 | 1 |
347 1day-1wk | 0 | 0 | 0 | 0 |
348 > 1wk | 0 | 0 | 0 | 0 |
349 |-------------------------------------------|
350 RWrite: 354287190 Backup: 354287192
352 server fs4.abc.com partition /vicepc RW Site
354 =head1 PRIVILEGE REQUIRED
360 L<backup_diskrestore(8)>,
361 L<backup_volrestore(8)>,
373 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
375 This documentation is covered by the IBM Public License Version 1.0. It was
376 converted from HTML to POD by software written by Chas Williams and Russ
377 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.