I've installed Coda-server and Coda-client and friends on my Debian
box with the deb packages (note: using the ftp server as a source in
/etc/apt/source-list doesn't work quite right, but on to the subject
at hand).

I created a root volume (replicated) and I was getting an error from
`volutil info root-vol`, Unknown RPC return code 103.  If I gave it a
bad volume name, the RPC return code was 22.  Venus was returning
"mount system call failed" during its startup.  I also created a
second replicated volume 'test1' before trying to start Venus.

I notice that others have reported "mount system call failed", without
resolution.  Hm, shutdown the server, restart the server (not the
udpate/client/auth2).

I then created a new volume 'ftwo', just to see if I could.  Sure
enough, it allowed me.  Now volutil info root-vol spits out some
information, and gives me information also about the new volume I
created.  However, `volutil info test1` still returns unknown RPC
return code 103.

VRList sez:

    ftw 7f000000 1 1000001 0 0 0 0 0 0 0 E0000100
    test1 7f000001 1 1000002 0 0 0 0 0 0 0 E0000100
    ftwo 7f000002 1 1000001 0 0 0 0 0 0 0 E0000100

Trying to remove the ftwo with volutil purge:

    # volutil purge 7f000002 ftwo
    V_BindToServer: binding to host backup
    VolPurge failed with Unknown RPC2 return code 103

What the heck? what's the problem?!?  What volumes does the system
*see*?

    # volutil getvolumelist
    V_BindToServer: binding to host backup
    P/vicepa Hbackup T84f350 F84f33c
    Wftwo.0 I1000001 H1 P/vicepa m0 M0 U2 W1000001 C3bc33ae8 D3bc33ae8
B0 A0
    GetVolumeList finished successfully

Uh... where's my root-vol?  Is what I'm wondering.

I hope that this report is detailed enough to show what I did and to
maybe reproduce the problem there at CMU.

Any more information or suggestions anybody has would certainly be
appreciated.

Randy