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.
If a newly created volume, when mounted dangling linkfor 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.
There exists a process with an reference to a file in /coda. Its
"unable to unmount" messageeither a running process cd-ed into
/coda 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.
Use the -console filename option to startcodav on startup. This will force stderr messages to print to the specified file. Use tail -f filename in a window to observe any error messages.
ABSOLUTE LAST RESORT If Rvm gets trashed -- it asserts, wont recover, there are many failures on salvage, dumpvm fails -- there are probably serious venus or srv bugs which must be fixed. Talk to Coda experts before continuing!!!
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.