Coda File System

Problems setting up Coda

From: Derek Glidden <>
Date: Tue, 16 Jan 2001 18:28:05 -0500
I am having the darnedest time getting Coda set up on one of my
servers.  It's pretty much a straight RedHat 6.2 box running on an
Athlon 700Mhz with 128MB of RAM and 256MB of swap set up.  

I've built the code from the latest CVS checkout (checked out just about
the time I was getting the "5.3.11" announcement in email) and installed
all the appropriate packages.  Everything builds and installs with no

Following instructions, I then run the "vice-setup" script, which as far
as I can tell all goes well.  Because of the server config I'm having to
use files for the Coda data and Coda log partitions, but that doesn't
seem to be related to the problem I'm having.

Then when it comes time to start the services and build the volume, I
can start auth2, rpc2portmap, updatesrv, updateclnt -h codabox,
startserver and everything runs.  I can see the server is up with: tail
/vice/srv/SrvLog and it looks like it's listening.  However, near the
top of the logfile, I see these messages, which seem to be related to
the failure of the volume creation:

18:03:30 VCheckVLDB:  could not open VLDB
18:03:30 VInitVolPackage: no VLDB! Please create a new one.
18:03:31 Vice file system salvager, version 3.0.
18:03:31 SanityCheckFreeLists: Checking RVM Vnode Free lists.
18:03:31 DestroyBadVolumes: Checking for destroyed volumes.
18:03:31 Attached 0 volumes; 0 volumes not attached
18:03:31 CheckVRDB: could not open VRDB

Then I get these messages when I run the command: 
createvol_rep codavol E0000100 /vicepa

Getting initial version of /vice/vol/BigVolumeList.
V_BindToServer: binding to host codabox
GetVolumeList finished successfully
Servers are (codabox )
V_BindToServer: binding to host codabox
GetVolumeList finished successfully
Found no partitions for server codabox.

And I can get no further.  I've looked through the "createvol_rep"
script and it seems to be having problems when it calls out to the
"" script. If I issue a "volutil getvolumelist" command like
the script does to build the VLDB file, it responds with: 

V_BindToServer: binding to host codabox
GetVolumeList finished successfully

which seems to indicate that the Coda server doesn't actually know of
any volumes it's supposed to have, which I think would be the reason I
can't actually create any.  The "BigVolumeList" file that is referenced
from so many places is always a 0-byte file.  I've tried removing the
file and re-running the various commands and all that ever happens is a
new 0-Byte file is recreated.  I also never get VRDB or VLDB files
anywhere in the /vice hierarchy.

If I ignore all that and just try to issue a "volutil create_rep"
command myself, it will fail with the messages:

V_BindToServer: binding to host codabox
VolCreate failed with Unknown RPC2 return code 103

I'm totally stuck and any help would be greatly appreciated. 

With Microsoft products, failure is not           Derek Glidden
an option - it's a standard component.
Choose your life.  Choose your  
future.  Choose Linux.    
Received on 2001-01-16 18:28:39