2005-12-08 12:14:33 +00:00
|
|
|
=head1 NAME
|
|
|
|
|
2007-11-11 22:54:56 +00:00
|
|
|
vos_move - Moves a read/write volume to another site
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
2006-03-01 05:02:29 +00:00
|
|
|
=for html
|
|
|
|
<div class="synopsis">
|
|
|
|
|
|
|
|
B<vos move> S<<< B<-id> <I<volume name or ID>> >>>
|
|
|
|
S<<< B<-fromserver> <I<machine name on source>> >>>
|
|
|
|
S<<< B<-frompartition> <I<partition name on source>> >>>
|
|
|
|
S<<< B<-toserver> <I<machine name on destination>> >>>
|
|
|
|
S<<< B<-topartition> <I<partition name on destination>> >>>
|
2009-10-08 18:31:00 +01:00
|
|
|
[B<-live>] 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>]
|
2005-12-09 14:48:56 +00:00
|
|
|
|
2006-03-01 05:02:29 +00:00
|
|
|
B<vos m> S<<< B<-i> <I<volume name or ID>> >>>
|
|
|
|
S<<< B<-froms> <I<machine name on source>> >>>
|
|
|
|
S<<< B<-fromp> <I<partition name on source>> >>>
|
|
|
|
S<<< B<-tos> <I<machine name on destination>> >>>
|
2009-10-08 18:31:00 +01:00
|
|
|
S<<< B<-top> <I<partition name on destination>> >>>
|
|
|
|
[B<-li>] S<<< [B<-c> <I<cell name>>] >>> [B<-noa>]
|
2013-06-20 23:45:05 +01:00
|
|
|
[B<-lo>] [B<-v>] [B<-e>] [B<-nor>]
|
|
|
|
S<<< [B<-co> <I<config directory>>] >>>
|
|
|
|
[B<-h>]
|
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 move> command moves the indicated read/write volume from its
|
|
|
|
current site (specified with the B<-fromserver> and B<-frompartition>
|
|
|
|
arguments) to the destination site (specified with the B<-toserver> and
|
|
|
|
B<-topartition> arguments). This command automatically removes the backup
|
|
|
|
copy from the current site, if it exists. To create a new backup volume at
|
|
|
|
the destination site, use the B<vos backup> command.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
This command works on read/write volumes only. To move a read-only volume,
|
|
|
|
use the B<vos addsite> and B<vos release> commands to define a new
|
|
|
|
read-only site and release the volume contents to it, and then use the
|
|
|
|
B<vos remove> command to remove the previous read-only volume's definition
|
|
|
|
from the Volume Location Database (VLDB) and data from the partition. To
|
|
|
|
move a backup volume, use this command to move its read/write source and
|
|
|
|
then issue the B<vos backup> command.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
Before executing this command, the B<vos> command interpreter initiates a
|
|
|
|
check that the destination partition contains enough space to house the
|
|
|
|
volume being moved. If there is not enough space, the move operation is
|
|
|
|
not attempted and the following message appears:
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
vos: no space on target partition <dest_part> to move volume <volume>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=head1 CAUTIONS
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
Unless there is a compelling reason, do not interrupt a B<vos move>
|
|
|
|
command in progress. Interrupting a move can result in one or more of the
|
|
|
|
following inconsistent states:
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
=item *
|
|
|
|
|
|
|
|
There are two versions of the volume, one at the source site and one at
|
2005-12-09 14:48:56 +00:00
|
|
|
the destination site. (If this happens, retain the version identified by
|
|
|
|
the VLDB and use the B<vos zap> command to remove the other version.)
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=item *
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The backup version of the volume is stranded at the old site. (If this
|
|
|
|
happens, use the B<vos zap> command to remove it.)
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=item *
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The volume is off-line. (If this happens, run the B<bos salvage> command
|
|
|
|
to bring it back on line.)
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=back
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
If the Ctrl-C interrupt signal is pressed while a vos move operation is
|
|
|
|
executing, the following message warns of the consequences and requests
|
|
|
|
confirmation of the kill signal:
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
SIGINT handler: vos move operation in progress
|
|
|
|
WARNING: may leave AFS storage and metadata in indeterminate state
|
|
|
|
enter second control-c to exit
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
To confirm termination of the operation, press Ctrl-C a second time; press
|
|
|
|
any other key to continue the operation.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2012-06-28 21:30:40 +01:00
|
|
|
=include fragments/volsize-caution.pod
|
2008-01-20 00:06:49 +00:00
|
|
|
|
2005-12-08 12:14:33 +00:00
|
|
|
=head1 OPTIONS
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-id> <I<volume name or ID>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Specifies either the complete name or volume ID number of a read/write
|
|
|
|
volume.
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-fromserver> <I<server name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Identifies the file server machine where the volume currently
|
2005-12-09 14:48:56 +00:00
|
|
|
resides. Provide the machine's IP address or its host name (either fully
|
|
|
|
qualified 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<-frompartition> <I<partition name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
Names the partition where the volume currently resides. Provide the full
|
|
|
|
partition name (for, example, B</vicepa>) or one of the abbreviated forms
|
|
|
|
described in L<vos(1)>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
=item B<-toserver> <I<server name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
Identifies the file server machine to which to move the volume. Provide
|
|
|
|
the machine's IP address or its host name (either fully qualified 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<-topartition> <I<partition name>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Names the partition to which to move the volume. Provide the full
|
2005-12-09 14:48:56 +00:00
|
|
|
partition name (for, example, B</vicepa>) or one of the abbreviated forms
|
|
|
|
described in L<vos(1)>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2007-12-25 22:15:07 +00:00
|
|
|
=item B<-live>
|
|
|
|
|
|
|
|
Avoids making a temporary copy of the volume during the move. This is
|
|
|
|
useful if the partition is full, but the administrator needs to move
|
|
|
|
volumes to a another partition or server to free up disk space. The
|
|
|
|
caveat is that the volume is locked during the entire operation
|
|
|
|
instead of the short time that is needed to make the temporary clone.
|
|
|
|
|
2013-06-30 03:06:51 +01:00
|
|
|
=include fragments/vos-common.pod
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=back
|
|
|
|
|
|
|
|
=head1 EXAMPLES
|
|
|
|
|
2005-12-09 14:48:56 +00:00
|
|
|
The following example moves the volume C<user.smith> from the F</vicepb>
|
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
|
|
|
partition on the file server machine C<fs3.example.com> to the F</vicepg>
|
|
|
|
partition on the file server machine C<fs7.example.com>.
|
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 move -id user.smith -fromserver fs3.example.com -frompartition b \
|
|
|
|
-toserver fs7.example.com -topartition g
|
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
|
|
|
|
machines specified with the B<-toserver> and B<-fromserver> arguments 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_addsite(1)>,
|
|
|
|
L<vos_backup(1)>,
|
2007-12-25 22:15:07 +00:00
|
|
|
L<vos_copy(1)>,
|
2005-12-08 12:14:33 +00:00
|
|
|
L<vos_release(1)>,
|
|
|
|
L<vos_listvol(1)>,
|
|
|
|
L<vos_remove(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.
|