2005-12-08 12:14:33 +00:00
|
|
|
=head1 NAME
|
|
|
|
|
2007-11-11 22:54:56 +00:00
|
|
|
vos_zap - Removes a volume from its site without writing to the VLDB
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
2006-03-01 05:02:29 +00:00
|
|
|
=for html
|
|
|
|
<div class="synopsis">
|
|
|
|
|
2009-10-08 18:31:00 +01:00
|
|
|
B<vos zap> S<<< B<-server> <I<machine name>> >>>
|
|
|
|
S<<< B<-partition> <I<partition name>> >>>
|
|
|
|
S<<< B<-id> <I<volume ID>> >>>
|
|
|
|
[B<-force>] [B<-backup>]
|
|
|
|
S<<< [B<-cell> <I<cell name>>] >>>
|
|
|
|
[B<-noauth>] [B<-localauth>]
|
2013-06-20 23:45:05 +01:00
|
|
|
[B<-verbose>] [B<-encrypt>] [B<-noresolve>]
|
|
|
|
S<<< [B<-config> <I<config directory>>] >>>
|
|
|
|
[B<-help>]
|
2009-10-08 18:31:00 +01:00
|
|
|
|
|
|
|
B<vos z> S<<< B<-s> <I<machine name>> >>>
|
|
|
|
S<<< B<-p> <I<partition name>> >>>
|
|
|
|
S<<< B<-i> <I<volume ID>> >>>
|
|
|
|
[B<-f>] [B<-b>] S<<< [B<-c> <I<cell name>>] >>>
|
2013-06-20 23:45:05 +01:00
|
|
|
[B<-noa>] [B<-l>] [B<-v>] [B<-e>] [B<-nor>]
|
|
|
|
S<<< [B<-co> <I<config directory>>] >>>
|
|
|
|
[B<-h>]
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2006-03-01 05:02:29 +00:00
|
|
|
=for html
|
|
|
|
</div>
|
|
|
|
|
2005-12-08 12:14:33 +00:00
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The B<vos zap> command removes the volume with the specified I<volume ID>
|
|
|
|
from the site defined by the B<-server> and B<-partition> arguments,
|
|
|
|
without attempting to change the corresponding Volume Location Database
|
|
|
|
(VLDB) entry. If removing the volume can possibly result in incorrect data
|
|
|
|
in the VLDB, a warning message is displayed.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The B<-force> flag removes a volume even if it cannot be "attached"
|
2005-12-08 12:14:33 +00:00
|
|
|
(brought online), which can happen either because the volume is extremely
|
2005-12-09 14:48:56 +00:00
|
|
|
damaged or because the Salvager functioned abnormally. Without this flag,
|
|
|
|
this command cannot remove volumes that are not attachable. See also
|
2011-06-10 02:14:05 +01:00
|
|
|
L</CAUTIONS>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
To remove the specified read/write volume's backup version at the same
|
|
|
|
time, include the B<-backup> flag.
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=head1 CAUTIONS
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Do not use this command as the standard way to remove a volume, as it is
|
|
|
|
likely to put the VLDB out of sync with the volumes on servers. Use the
|
|
|
|
B<vos remove> command instead.
|
|
|
|
|
|
|
|
This command is useful in situations where it is important to delete the
|
2005-12-09 14:48:56 +00:00
|
|
|
volume, but for some reason the VLDB is unreachable -- for example,
|
2009-07-07 02:26:30 +01:00
|
|
|
because the Volume Location Server is unavailable. The issuer can remove
|
2005-12-09 14:48:56 +00:00
|
|
|
the VLDB entry later with the B<vos remove> or B<vos delentry> command, or
|
|
|
|
it is removed automatically when the B<vos syncserv> and B<vos syncvldb>
|
|
|
|
commands run.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
To remove a read-only site defined in the VLDB by mistake, before a copy
|
2005-12-09 14:48:56 +00:00
|
|
|
actually exists at the site, use the B<vos remsite> command. To remove an
|
|
|
|
entire VLDB entry without affecting volumes at their sites, use the B<vos
|
|
|
|
delentry> command.
|
|
|
|
|
|
|
|
Do not use the B<-force> flag if the volume is online, but only when
|
|
|
|
attempts to remove the volume with the B<vos remove> or the B<vos zap>
|
|
|
|
command have failed, or the volume definitely cannot be attached. After
|
|
|
|
using the B<-force> flag, make sure that the volume's VLDB entry is also
|
|
|
|
removed (issue the B<vos delentry> command if necessary).
|
|
|
|
|
|
|
|
Adding the B<-force> flag makes the command take considerably longer --
|
|
|
|
about as long as a salvage of the relevant partition -- since the Volume
|
|
|
|
Server examines all inodes on the partition for traces of the volume.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=head1 OPTIONS
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-server> <I<server name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Identifies the file server machine from which to remove the volume.
|
|
|
|
Provide the machine's IP address or its host name (either fully qualified
|
2005-12-09 14:48:56 +00:00
|
|
|
or using an unambiguous abbreviation). For details, see L<vos(1)>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-partition> <I<partition name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Identifies the partition (on the file server machine specified by the
|
2005-12-09 14:48:56 +00:00
|
|
|
B<-server> argument) from which to remove the volume. Provide the
|
|
|
|
partition's complete name with preceding slash (for example, C</vicepa>)
|
|
|
|
or use one of the three acceptable abbreviated forms. For details, see
|
|
|
|
L<vos(1)>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-id> <I<volume ID>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Specifies the volume ID number of the volume to remove, which can be of
|
|
|
|
any of the three types. The volume name is not acceptable.
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-force>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
Removes the volume even though it cannot be attached (brought online). Use
|
|
|
|
only after the failure of previous attempts to remove the volume by using
|
|
|
|
the B<vos remove> command or the B<vos zap> command without this flag.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-backup>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Removes the backup version of the read/write volume specified by the
|
2005-12-09 14:48:56 +00:00
|
|
|
B<-id> argument. Do not use this flag if the B<-id> argument identifies a
|
|
|
|
read-only or backup volume.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2010-08-02 02:39:56 +01:00
|
|
|
=include fragments/vos-common.pod
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=back
|
|
|
|
|
|
|
|
=head1 EXAMPLES
|
|
|
|
|
|
|
|
The following example removes the volume with volume ID 536870988 from the
|
doc: replace hostnames with IETF example hostnames
There were several different real and made-up hostnames and company names used
throughout our documentation examples.
The IETF has reserved "example.com" and other "example" TLDs for use in
examples (RFC 2606). Replace almost all references to ABC Corporation, DEF
Corporation, and State University, as well as "abc.com", "bigcell.com",
"def.com", "def.gov", "ghi.com", "ghi.gov", "jkl.com", "mit.edu",
"stanford.edu", "state.edu", "stateu.edu", "uncc.edu", and "xyz.com".
Standardize on "Example Corporation", "Example Network", "Example
Organization" (example.com, example.net, and example.org).
The Scout documentation in the Admin Guide contains PNG images that contain
the old cell names, so I left those references until the images can be
replaced.
Change-Id: I4e44815b2d2ffe204810b7fd850842248f67c367
Reviewed-on: http://gerrit.openafs.org/6697
Reviewed-by: Jeffrey Altman <jaltman@secure-endpoints.com>
Tested-by: Jeffrey Altman <jaltman@secure-endpoints.com>
2012-02-11 16:43:30 +00:00
|
|
|
F</vicepf> partition of the file server machine C<fs6.example.com>, without
|
2005-12-09 14:48:56 +00:00
|
|
|
noting the change in the VLDB.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
doc: replace hostnames with IETF example hostnames
There were several different real and made-up hostnames and company names used
throughout our documentation examples.
The IETF has reserved "example.com" and other "example" TLDs for use in
examples (RFC 2606). Replace almost all references to ABC Corporation, DEF
Corporation, and State University, as well as "abc.com", "bigcell.com",
"def.com", "def.gov", "ghi.com", "ghi.gov", "jkl.com", "mit.edu",
"stanford.edu", "state.edu", "stateu.edu", "uncc.edu", and "xyz.com".
Standardize on "Example Corporation", "Example Network", "Example
Organization" (example.com, example.net, and example.org).
The Scout documentation in the Admin Guide contains PNG images that contain
the old cell names, so I left those references until the images can be
replaced.
Change-Id: I4e44815b2d2ffe204810b7fd850842248f67c367
Reviewed-on: http://gerrit.openafs.org/6697
Reviewed-by: Jeffrey Altman <jaltman@secure-endpoints.com>
Tested-by: Jeffrey Altman <jaltman@secure-endpoints.com>
2012-02-11 16:43:30 +00:00
|
|
|
% vos zap -server fs6.example.com -partition f -id 536870988
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=head1 PRIVILEGE REQUIRED
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The issuer must be listed in the F</usr/afs/etc/UserList> file on the
|
|
|
|
machine specified with the B<-server> argument and on each database server
|
|
|
|
machine. If the B<-localauth> flag is included, the issuer must instead be
|
|
|
|
logged on to a server machine as the local superuser C<root>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
|
|
|
L<vos(1)>,
|
|
|
|
L<vos_delentry(1)>,
|
|
|
|
L<vos_remove(1)>,
|
|
|
|
L<vos_remsite(1)>
|
|
|
|
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
|
|
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
|
|
|
|
|
|
|
|
This documentation is covered by the IBM Public License Version 1.0. It was
|
|
|
|
converted from HTML to POD by software written by Chas Williams and Russ
|
|
|
|
Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
|