VOS_CONVERTROTORW(1)

NAME
vos_convertROtoRW - Converts a Read-Only volume into a Read/Write volume

SYNOPSIS
vos convertROtoRW [-server] <machine name>
   [-partition] <partition name>
   [-id] <volume name or ID> [-force]
   [-cell <cell name>] [-noauth] [-localauth]
   [-verbose] [-encrypt] [-noresolve]
   [-config <config directory>]
   [-help]

vos con [-s] <machine name>
   [-p] <partition name>
   [-i] <volume name or ID> [-f]
   [-c <cell name>] [-noa] [-l]
   [-v] [-e] [-nor]
   [-co <config directory>]
   [-h]

DESCRIPTION
vos convertROtoRW converts a Read-Only volume into a Read/Write volume when the original Read/Write volume is no longer available. It's normal use is to recover the Read/Write volume from a replica after a failed disk, failed server, or accidental deletion.

CAUTIONS
The command name is case-sensitive. It must be issued with the capital "RO" and "RW".

After running vos convertROtoRW, the old file server will still contain the old Read/Write copy of the volume, even if the VLDB no longer references it. You can view the old volume with vos listvol, and you should remove the old copy (for example, with vos zap) so that the original file server will match the VLDB.

OPTIONS

-server <server name>
    Identifies the file server machine that houses the Read-Only volume which will be converted. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1).

-partition <partition name>
    Identifies the partition on the file server machine that houses the Read-Only volume which will be converted. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1).

-id <volume ID>
    Specifies either the complete name or volume ID number of a Read/Write volume.

-force
    Don't ask for confirmation.

-cell <cell name>
    Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1).

-noauth
    Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1).

-localauth
    Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1).

-verbose
    Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear.

-encrypt
    Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later.

-noresolve
    Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later.

-config <configuration directory>
    Set the location of the configuration directory to be used. This defaults to /etc/openafs, except if -localauth is specified, in which case the default is /etc/openafs/server. This option allows the use of alternative configuration locations for testing purposes.

-help
    Prints the online help for this command. All other valid options are ignored.

EXAMPLES
The following example converts the read-only volume test3.readonly in partition vicepb on server1 to a read-write volume:

   % vos convertROtoRW server1 b test3.readonly

PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root".

SEE ALSO
vos(1)

COPYRIGHT
Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>

This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS.