Coda File System

Re: venus startup problems

From: Jan Harkes <jaharkes_at_cs.cmu.edu>
Date: Sun, 11 Jul 1999 15:18:15 -0400
On Sun, Jul 11, 1999 at 02:42:16PM -0400, thoth_at_purplefrog.com wrote:
> #9  0x80ac3df in choke (
>     file=0x8165e8f "/usr/src/redhat/BUILD/coda-5.2.4/coda-src/venus/comm.cc", 
>     line=252, fmt=0x8165f6e "CommInit: RPC2_Init failed")
>     at /usr/src/redhat/BUILD/coda-5.2.4/coda-src/venus/venusutil.cc:205
> #10 0x804f7ae in CommInit ()
>     at /usr/src/redhat/BUILD/coda-5.2.4/coda-src/venus/comm.cc:252
> #11 0x80afb92 in main (argc=2, argv=0xbffffa14)
>     at /usr/src/redhat/BUILD/coda-5.2.4/coda-src/venus/venus.cc:149

Hmm, RPC2_Init fails, either another server is already/still running, or
the codasrv/codasrv-se ports are missing from /etc/services.

> memo: calling a program "norton" might infringe upon somebody's
> trademark.  Depending on what it does, you might call it coda.editfs,
> or fsck.coda.  Pity the server RPM doesn't include manual pages, or I
> could tell what norton does.

Yes, it should be renamed. It can be used to edit/view several
fileserver structures in RVM. It is useful only in a few cases, to fix
up corrupt directory structures, or destroy volumes on which the server
crashes during recovery. In that way it is a bit like ext2's debugfs
program, which is sometimes the only way to fix really serious ext2fs
corruptions.

Jan
Received on 1999-07-11 15:18:57