mirror of
https://git.openafs.org/openafs.git
synced 2025-01-21 08:20:16 +00:00
188 lines
10 KiB
HTML
188 lines
10 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
|
||
|
|
<HTML><HEAD>
|
||
|
|
<TITLE>Administration Reference</TITLE>
|
||
|
|
<!-- Begin Header Records ========================================== -->
|
||
|
|
<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
|
||
|
|
<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
|
||
|
|
<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
|
||
|
|
<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
|
||
|
|
<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
|
||
|
|
</HEAD><BODY>
|
||
|
|
<!-- (C) IBM Corporation 2000. All Rights Reserved -->
|
||
|
|
<BODY bgcolor="ffffff">
|
||
|
|
<!-- End Header Records ============================================ -->
|
||
|
|
<A NAME="Top_Of_Page"></A>
|
||
|
|
<H1>Administration Reference</H1>
|
||
|
|
<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf269.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf271.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
|
||
|
|
<P>
|
||
|
|
<H2><A NAME="HDRVOS_RELEASE" HREF="auarf002.htm#ToC_284">vos release</A></H2>
|
||
|
|
<A NAME="IDX5782"></A>
|
||
|
|
<A NAME="IDX5783"></A>
|
||
|
|
<A NAME="IDX5784"></A>
|
||
|
|
<A NAME="IDX5785"></A>
|
||
|
|
<A NAME="IDX5786"></A>
|
||
|
|
<A NAME="IDX5787"></A>
|
||
|
|
<A NAME="IDX5788"></A>
|
||
|
|
<A NAME="IDX5789"></A>
|
||
|
|
<A NAME="IDX5790"></A>
|
||
|
|
<A NAME="IDX5791"></A>
|
||
|
|
<A NAME="IDX5792"></A>
|
||
|
|
<A NAME="IDX5793"></A>
|
||
|
|
<A NAME="IDX5794"></A>
|
||
|
|
<A NAME="IDX5795"></A>
|
||
|
|
<A NAME="IDX5796"></A>
|
||
|
|
<A NAME="IDX5797"></A>
|
||
|
|
<A NAME="IDX5798"></A>
|
||
|
|
<A NAME="IDX5799"></A>
|
||
|
|
<A NAME="IDX5800"></A>
|
||
|
|
<A NAME="IDX5801"></A>
|
||
|
|
<A NAME="IDX5802"></A>
|
||
|
|
<A NAME="IDX5803"></A>
|
||
|
|
<A NAME="IDX5804"></A>
|
||
|
|
<P><STRONG>Purpose</STRONG>
|
||
|
|
<P>Updates the contents of read-only volumes to match their read/write source
|
||
|
|
volume
|
||
|
|
<P><STRONG>Synopsis</STRONG>
|
||
|
|
<PRE><B>vos release -id</B> <<VAR>volume name or ID</VAR>> [<B>-f</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
|
||
|
|
[<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
|
||
|
|
|
||
|
|
<B>vos rel -i</B> <<VAR>volume name or ID</VAR>> [<B>-f</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
|
||
|
|
</PRE>
|
||
|
|
<P><STRONG>Description</STRONG>
|
||
|
|
<P>The <B>vos release</B> command copies the contents of the indicated
|
||
|
|
read/write source volume to each read-only site defined in the source
|
||
|
|
volume's Volume Location Database (VLDB) entry. (Use the <B>vos
|
||
|
|
addsite</B> command to define sites as necessary before issuing this
|
||
|
|
command). Each read-only copy has the same name as read/write source
|
||
|
|
with the addition of a <B>.readonly</B> extension.
|
||
|
|
<P>For users to have a consistent view of the file system, the release of the
|
||
|
|
new volume version must be atomic: either all read-only sites receive
|
||
|
|
the new version, or all sites keep the version they currently have. The
|
||
|
|
<B>vos release</B> command is designed to ensure that all copies of the
|
||
|
|
volume's read-only version match both the read/write source and each
|
||
|
|
other. In cases where problems such as machine or server process
|
||
|
|
outages prevent successful completion of the release operation, AFS uses two
|
||
|
|
mechanisms to alert the administrator.
|
||
|
|
<P>First, the command interpreter generates an error message on the standard
|
||
|
|
error stream naming each read-only site that did not receive the new volume
|
||
|
|
version. Second, during the release operation the Volume Location (VL)
|
||
|
|
Server marks site definitions in the VLDB entry with flags (<TT>New
|
||
|
|
release</TT> and <TT>Old release</TT>) that indicate whether or not the
|
||
|
|
site has the new volume version. If any flags remain after the
|
||
|
|
operation completes, it was not successful. The Cache Manager refuses
|
||
|
|
to access a read-only site marked with the <TT>Old release</TT> flag, which
|
||
|
|
potentially imposes a greater load on the sites marked with the <TT>New
|
||
|
|
release</TT> flag. It is important to investigate and eliminate the
|
||
|
|
cause of the failure and then to issue the <B>vos release</B> command as
|
||
|
|
many times as necessary to complete the release without errors.
|
||
|
|
<P>The pattern of site flags remaining in the volume's VLDB entry after a
|
||
|
|
failed release operation can help determine the point at which the operation
|
||
|
|
failed. Use the <B>vos examine</B> or <B>vos listvldb</B>
|
||
|
|
command to display the VLDB entry. The VL Server sets the flags in
|
||
|
|
concert with the Volume Server's operations, as follows:
|
||
|
|
<OL TYPE=1>
|
||
|
|
<P><LI>Before the operation begins, the VL Server sets the <TT>New release</TT>
|
||
|
|
flag on the read/write site definition in the VLDB entry and the <TT>Old
|
||
|
|
release</TT> flag on read-only site definitions (unless the read-only site
|
||
|
|
has been defined since the last release operation and has no actual volume, in
|
||
|
|
which case its site flag remains <TT>Not released</TT>).
|
||
|
|
<P><LI>If necessary, the Volume Server creates a temporary copy (a
|
||
|
|
<I>clone</I>) of the read/write source called the ReleaseClone (see the
|
||
|
|
following discussion of when the Volume Server does or does not create a new
|
||
|
|
ReleaseClone.) It assigns the ReleaseClone its own volume ID number,
|
||
|
|
which the VL Server records in the <TT>RClone</TT> field of the source
|
||
|
|
volume's VLDB entry.
|
||
|
|
<P><LI>The Volume Server distributes a copy of the ReleaseClone to each read-only
|
||
|
|
site defined in the VLDB entry. As the site successfully receives the
|
||
|
|
new clone, the VL Server sets the site's flag in the VLDB entry to
|
||
|
|
<TT>New release</TT>.
|
||
|
|
<P><LI>When all the read-only copies are successfully released, the VL Server
|
||
|
|
clears all the <TT>New release</TT> site flags. The ReleaseClone is
|
||
|
|
no longer needed, so the Volume Server deletes it and the VL Server erases its
|
||
|
|
ID from the VLDB entry.
|
||
|
|
</OL>
|
||
|
|
<P>By default, the Volume Server determines automatically whether or not it
|
||
|
|
needs to create a new ReleaseClone:
|
||
|
|
<UL>
|
||
|
|
<P><LI>If there are no flags (<TT>New release</TT>, <TT>Old release</TT>, or
|
||
|
|
<TT>Not released</TT>) on site definitions in the VLDB entry, the previous
|
||
|
|
<B>vos release</B> command completed successfully and all read-only sites
|
||
|
|
currently have the same volume. The Volume Server infers that the
|
||
|
|
current <B>vos release</B> command was issued because the read/write
|
||
|
|
volume has changed. The Volume Server creates a new ReleaseClone and
|
||
|
|
distributes it to all of the read-only sites.
|
||
|
|
<P><LI>If any site definition in the VLDB entry is marked with a flag, either the
|
||
|
|
previous release operation did not complete successfully or a new read-only
|
||
|
|
site was defined since the last release. The Volume Server does not
|
||
|
|
create a new ReleaseClone, instead distributing the existing ReleaseClone to
|
||
|
|
sites marked with the <TT>Old release</TT> or <TT>Not released</TT>
|
||
|
|
flag. As previously noted, the VL Server marks each VLDB site
|
||
|
|
definition with the <TT>New release</TT> flag as the site receives the
|
||
|
|
ReleaseClone, and clears all flags after all sites successfully receive
|
||
|
|
it.
|
||
|
|
</UL>
|
||
|
|
<P>To override the default behavior, forcing the Volume Server to create and
|
||
|
|
release a new ReleaseClone to the read-only sites, include the <B>-f</B>
|
||
|
|
flag. This is appropriate if, for example, the data at the read/write
|
||
|
|
site has changed since the existing ReleaseClone was created during the
|
||
|
|
previous release operation.
|
||
|
|
<P><STRONG>Options</STRONG>
|
||
|
|
<DL>
|
||
|
|
<P><DT><B>-id
|
||
|
|
</B><DD>Specifies either the complete name or volume ID number of a read/write
|
||
|
|
volume.
|
||
|
|
<P><DT><B>-f
|
||
|
|
</B><DD>Creates a new ReleaseClone and distributes it all read-only sites
|
||
|
|
regardless of whether or not any site definitions in the VLDB entry are marked
|
||
|
|
with a flag.
|
||
|
|
<P><DT><B>-cell
|
||
|
|
</B><DD>Names the cell in which to run the command. Do not combine this
|
||
|
|
argument with the <B>-localauth</B> flag. For more details, see the
|
||
|
|
introductory <B>vos</B> reference page.
|
||
|
|
<P><DT><B>-noauth
|
||
|
|
</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
|
||
|
|
issuer. Do not combine this flag with the <B>-localauth</B>
|
||
|
|
flag. For more details, see the introductory <B>vos</B> reference
|
||
|
|
page.
|
||
|
|
<P><DT><B>-localauth
|
||
|
|
</B><DD>Constructs a server ticket using a key from the local
|
||
|
|
<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
|
||
|
|
interpreter presents it to the Volume Server and Volume Location Server during
|
||
|
|
mutual authentication. Do not combine this flag with the
|
||
|
|
<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
|
||
|
|
see the introductory <B>vos</B> reference page.
|
||
|
|
<P><DT><B>-verbose
|
||
|
|
</B><DD>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.
|
||
|
|
<P><DT><B>-help
|
||
|
|
</B><DD>Prints the online help for this command. All other valid options
|
||
|
|
are ignored.
|
||
|
|
</DL>
|
||
|
|
<P><STRONG>Examples</STRONG>
|
||
|
|
<P>The following command clones the read/write volume <B>usr</B> and
|
||
|
|
releases it to the read-only sites defined in its VLDB entry.
|
||
|
|
<PRE> % <B>vos release usr</B>
|
||
|
|
|
||
|
|
</PRE>
|
||
|
|
<P><STRONG>Privilege Required</STRONG>
|
||
|
|
<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
|
||
|
|
the machine specified with the <B>-server</B> argument and on each
|
||
|
|
database server machine. If the <B>-localauth</B> flag is included,
|
||
|
|
the issuer must instead be logged on to a server machine as the local
|
||
|
|
superuser <B>root</B>.
|
||
|
|
<P><STRONG>Related Information</STRONG>
|
||
|
|
<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
|
||
|
|
<P><A HREF="auarf253.htm#HDRVOS_ADDSITE">vos addsite</A>
|
||
|
|
<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
|
||
|
|
<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
|
||
|
|
<P>
|
||
|
|
<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf269.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf271.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
|
||
|
|
<!-- Begin Footer Records ========================================== -->
|
||
|
|
<P><HR><B>
|
||
|
|
<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
|
||
|
|
</B>
|
||
|
|
<!-- End Footer Records ============================================ -->
|
||
|
|
<A NAME="Bot_Of_Page"></A>
|
||
|
|
</BODY></HTML>
|