Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod1 / vos_listvol.pod.in
CommitLineData
805e021f
CE
1=head1 NAME
2
3vos_listvol - Displays information from a volume header
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<vos listvol> S<<< B<-server> <I<machine name>> >>>
11 S<<< [B<-partition> <I<partition name>>] >>>
12 [B<-fast>] [B<-long>] [B<-quiet>]
13 [B<-extended>] [B<-format>]
14 S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>]
15 [B<-verbose>] [B<-encrypt>] [B<-noresolve>]
16 S<<< [B<-config> <I<config directory>>] >>>
17 [B<-help>]
18
19B<vos listvo> S<<< B<-s> <I<machine name>> >>>
20 S<<< [B<-p> <I<partition name>>] >>>
21 [B<-fa>] [-lon] [B<-q>] [B<-ex>] [B<-fo>]
22 S<<< [B<-c> <I<cell name>>] >>>
23 [B<-noa>] [B<-loc>] [B<-v>] [B<-en>] [B<-nor>]
24 S<<< [B<-co> <I<config directory>>] >>>
25 [B<-h>]
26
27=for html
28</div>
29
30=head1 DESCRIPTION
31
32The B<vos listvol> command formats and displays the following information
33from the volume header of each specified volume: volume name, volume ID,
34volume type, size, and status at the server. The actual information
35displayed depends on the combination of arguments supplied when the
36command is issued. To display volume header information for various
37numbers of volumes, combine the command's arguments as indicated:
38
39=over 4
40
41=item *
42
43For every volume on a file server machine, specify the machine's name with
44the B<-server> argument.
45
46=item *
47
48For every volume at a particular site, combine the B<-server> argument
49with the B<-partition> argument.
50
51=back
52
53To display the Volume Location Database (VLDB) entry for one or more
54volumes, use the B<vos listvldb> command. To display both the VLDB entry
55and the volume header for a single volume, use the B<vos examine> command.
56
57=head1 OPTIONS
58
59=over 4
60
61=item B<-server> <I<server name>>
62
63Identifies the file server machine that houses volumes for which to
64display the header. Provide the machine's IP address or its host name
65(either fully qualified or using an unambiguous abbreviation). For
66details, see L<vos(1)>.
67
68This argument can be combined with the B<-partition> argument, as well as
69the B<-fast>, B<-long>, or B<-extended> flag.
70
71=item B<-partition> <I<partition name>>
72
73Identifies the partition (on the file server machine specified by the
74B<-server> argument) that houses volumes for which to display the
75header. Provide the partition's complete name with preceding slash (for
76example, F</vicepa>) or use one of the three acceptable abbreviated
77forms. For details, see L<vos(1)>.
78
79=item B<-fast>
80
81Displays only the volume ID numbers of volumes stored at the site
82specified by the B<-server>, and optionally B<-partition>, argument. Do
83not combine this flag with the B<-extended> flag.
84
85=item B<-long>
86
87Displays more detailed information about each volume stored at the site
88specified by the B<-server>, and optionally B<-partition>, argument. The
89information includes the volume IDs of all three volume types associated
90with the volume, and the read/write volume's quota, creation date and
91update date.
92
93=item B<-quiet>
94
95Suppresses the lines that summarize the number of volumes listed and their
96status, which otherwise appear at the beginning and end of the output when
97the output includes more than one volume.
98
99=item B<-extended>
100
101Displays extensive statistics about access patterns for each volume stored
102at the site specified by the B<-server>, and optionally B<-partition>,
103argument. The statistics include the number of reads and writes to files
104in the volume, and how recently files and directories have been updated by
105their owners or other users. Do not combine this flag with the B<-fast>
106flag.
107
108=item B<-format>
109
110Show information in a format suitable for machine parsing.
111
112=include fragments/vos-common.pod
113
114=back
115
116=head1 OUTPUT
117
118The output is ordered alphabetically by volume name and by default
119provides the following information on a single line for each volume:
120
121=over 4
122
123=item *
124
125Name
126
127=item *
128
129Volume ID number
130
131=item *
132
133Type (the flag is C<RW> for read/write, C<RO> for read-only, C<BK> for
134backup)
135
136=item *
137
138Size in kilobytes (C<1024> equals a megabyte)
139
140=item *
141
142Number of files in the volume, if the B<-extended> flag is provided
143
144=item *
145
146Status on the file server machine, which is one of the following:
147
148=over 4
149
150=item On-line
151
152The volume is completely accessible to Cache Managers.
153
154=item Off-line
155
156The volume is not accessible to Cache Managers, but does not seem to be
157corrupted. This status appears while a volume is being dumped, for
158example.
159
160=item Off-line**needs salvage**
161
162The volume is not accessible to Cache Managers, because it seems to be
163corrupted. Use the B<bos salvage> or B<salvager> command to repair the
164corruption.
165
166=back
167
168=back
169
170If the following message appears instead of the previously listed
171information, it indicates that a volume is not accessible to Cache
172Managers or the B<vos> command interpreter, for example because a clone is
173being created.
174
175 **** Volume <volume_ID> is busy ****
176
177If the following message appears instead of the previously listed
178information, it indicates that the File Server is unable to attach the
179volume, perhaps because it is seriously corrupted. The F<FileLog> and
180F<VolserLog> log files in the F</usr/afs/logs> directory on the file
181server machine possibly provide additional information; use the B<bos
182getlog> command to display them.
183
184 **** Could not attach volume <volume_ID> ****
185
186The information about individual volumes is bracketed by summary
187lines. The first line of output specifies the number of volumes in the
188listing. The last line of output summarizes the number of volumes that are
189online, offline, and busy. These lines do not appear if the B<-quiet> flag
190is used.
191
192If the B<-fast> flag is added, the output displays only the volume ID
193number of each volume, arranged in increasing numerical order. The final
194line (which summarizes the number of online, offline, and busy volumes) is
195omitted.
196
197If the B<-long> flag is included, the output for each volume includes all
198of the information in the default listing plus the following. Each item in
199this list corresponds to a separate line of output:
200
201=over 4
202
203=item *
204
205The file server machine and partition that house the volume, as determined
206by the command interpreter as the command runs, rather than derived from the
207VLDB or the volume header.
208
209=item *
210
211The volume ID numbers associated with the various versions of the volume:
212read/write (C<RWrite>), read-only (C<ROnly>), backup (C<Backup>), and
213ReleaseClone (C<RClone>). One of them matches the volume ID number that
214appears on the first line of the volume's output. If the value in the
215C<RWrite>, C<ROnly>, or C<Backup> field is C<0> (zero), there is no volume
216of that type. If there is currently no ReleaseClone, the C<RClone> field
217does not appear at all.
218
219=item *
220
221The maximum space quota allotted to the read/write copy of the volume,
222expressed in kilobyte blocks in the C<MaxQuota> field.
223
224=item *
225
226The date and time the volume was created, in the C<Creation> field. If the
227volume has been restored with the B<backup diskrestore>, B<backup
228volrestore>, or B<vos restore> command, this is the restore time.
229
230=item *
231
232The date and time when the contents of the volume last changed, in the
233C<Last Update> field. For read-only and backup volumes, it matches the
234timestamp in the C<Creation> field.
235
236=item *
237
238The number of times the volume has been accessed for a fetch or store
239operation since the later of the two following times:
240
241=over 4
242
243=item *
244
24512:00 a.m. on the day the command is issued
246
247=item *
248
249The last time the volume changed location
250
251=back
252
253=back
254
255If the B<-extended> flag is included, the output for each volume includes
256all of the information reported with the B<-long> flag, plus two tables of
257statistics:
258
259=over 4
260
261=item *
262
263The table labeled C<Raw Read/Write Stats> table summarizes the number of
264times the volume has been accessed for reading or writing.
265
266=item *
267
268The table labeled C<Writes Affecting Authorship> table contains
269information on writes made to files and directories in the specified
270volume.
271
272=back
273
274=head1 EXAMPLES
275
276The following example shows the output for the F</vicepb> partition on the
277file server machine C<fs2.example.com> when no flags are provided:
278
279 % vos listvol -server fs2.example.com -partition b
280 Total number of volumes on server fs2.example.com partition /vicepb : 66
281 sys 1969534847 RW 1582 K On-line
282 sys.backup 1969535105 BK 1582 K On-line
283 . . . . . .
284 . . . . . .
285 user.pat 1969534536 RW 17518 K On-line
286 user.pat.backup 1969534538 BK 17537 K On-line
287 Total volumes onLine 66 ; Total volumes offLine 0 ; Total busy 0
288
289The following example shows the output when the B<-fast> flag is added:
290
291 % vos listvol -server fs2.example.com -partition b -fast
292 Total number of volumes on server fs2.example.com partition /vicepb : 66
293 1969516782
294 1969516784
295 .
296 .
297 1969535796
298
299The following example shows two volumes from the output that appears when
300the B<-long> flag is added:
301
302 % vos listvol -server fs2.example.com -partition b -long
303 Total number of volumes on server fs2.example.com partition /vicepb: 66
304 . . . . . .
305 . . . . . .
306 user.pat 1969534536 RW 17518 K On-line
307 fs2.example.com /vicepb
308 RWrite 1969534536 ROnly 0 Backup 1969534538
309 MaxQuota 20000 K
310 Creation Mon Jun 12 09:02:25 1989
311 Last Update Thu May 20 17:39:34 1999
312 1573 accesses in the past day (i.e., vnode references)
313 user.pat.backup 1969534538 BK 17537 K On-line
314 fs2.example.com /vicepb
315 RWrite 1969534536 ROnly 0 Backup 1969534538
316 MaxQuota 20000 K
317 Creation Tue Jun 13 04:37:59 1989
318 Last Update Wed May 19 06:37:59 1999
319 0 accesses in the past day (i.e., vnode references)
320 . . . . . .
321 . . . . . .
322 Total volumes onLine 66 ; Total volumes offLine 0 ; Total busy 0
323
324=head1 PRIVILEGE REQUIRED
325
326None
327
328=head1 SEE ALSO
329
330L<backup_diskrestore(8)>,
331L<backup_volrestore(8)>,
332L<bos_getlog(8)>,
333L<bos_salvage(8)>,
334L<salvager(8)>,
335L<vos(1)>,
336L<vos_examine(1)>,
337L<vos_listvldb(1)>,
338L<vos_restore(1)>
339
340=head1 COPYRIGHT
341
342IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
343
344This documentation is covered by the IBM Public License Version 1.0. It was
345converted from HTML to POD by software written by Chas Williams and Russ
346Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.