Sophie: coda-doc-5.2.0-4mdk noarch

coda-doc-5.2.0-4mdk.noarch.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE>Coda File System  User and System Administrators Manual: Common Problems and Suggestions                        </TITLE>
 <LINK HREF="manual-18.html" REL=next>
 <LINK HREF="manual-16.html" REL=previous>
 <LINK HREF="manual.html#toc17" REL=contents>
</HEAD>
<BODY>
<A HREF="manual-18.html">Next</A>
<A HREF="manual-16.html">Previous</A>
<A HREF="manual.html#toc17">Contents</A>
<HR>
<H2><A NAME="Problems"></A> <A NAME="s17">17. Common Problems and Suggestions                        </A></H2>

<P>                                                     
<P>
<DL>
<DT><B><B><CODE>ls /coda</CODE> fails</B></B><DD><P>If the return code is either 
"Invalid Argument" or "No Device", venus was probably restarted recently 
and hasnt yet finished initializing. Solution:  Wait a few minutes a try again.
<DT><B><B>Newly created volume is</B></B><DD><P>If a newly created volume, when mounted
<B>dangling link</B>for the first time, shows up as a dangling symbolic 
link (it looks inconsistent), the problem is that new databases have 
not been distributed to the other replication sites.  Solution:  Unmount 
the volume, wait five minutes and try again. You'll have to reinitialize 
the venus which failed to find the volume, since vldb information 
cant be flushed.
<DT><B><B>Venus Fails on Startup with</B> </B><DD><P>There exists a process with an reference to a file in /coda. Its
<B>"unable to unmount" message</B>either a running process <B>cd</B>-ed into <CODE>/coda</CODE> To solve
the problem, either get the process out of /coda (in case its
a shell) or kill it the process. If you cant find the right process
rebooting the workstation should clear it up.
<DT><B><B>Venus error messages fail to print on console window of window manager</B></B><DD><P>Use the <EM>-console filename</EM> option to <B>startcodav</B> on startup.
This will force stderr messages to print to the specified file.
Use <B>tail -f filename</B> in a window to observe any error messages.
<DT><B><B>Rvm gets Trashed</B></B><DD><P><B>ABSOLUTE LAST RESORT</B>
If Rvm gets trashed -- it asserts, wont recover, there are many failures
on salvage, dumpvm fails -- there are probably serious <B>venus</B> or <B>srv</B>
bugs which must be fixed. Talk to Coda experts before continuing!!!
<DT><B><B>Performing the following actions will result in the loss of ALL Coda file system data.</B></B><DD><P>Reinitializing the RVM Data segment (i.e. with rdsinit)
Reinitializing the RVM Log (i.e. with rvmutl)
Rewriting or trashing the file containing the Log or Data segment.
</DL>
<HR>
<A HREF="manual-18.html">Next</A>
<A HREF="manual-16.html">Previous</A>
<A HREF="manual.html#toc17">Contents</A>
</BODY>
</HTML>