On Wed, Feb 09, 2000 at 03:23:10PM -0800, Quinn Weaver wrote:
> worked!  It must have taken some time to let go of the reference to
> /dev/cfs0.  Weird.  Now it prints the following:
> 
> root_at_boc# venus -init
...
> 14:56:31 Initial LRDB allocation
> 14:56:31 Getting Root Volume information...
> Killed

Either /coda is still mounted, or the rootvolume does not exist,
although I though it simply keeps on trying in that case.

Run 'umount /coda' before restarting venus.

> root_at_boc:/etc/rc.d/rc3.d# createvol_rep coda_root E0000100 /vicepa/
> Servers are (boc )
> HexGroupId is 7F000006
> creating volume coda_root.0 on boc
> V_BindToServer: binding to host boc.private.vovida.com
> VolCreate failed with Unknown RPC2 return code 103
> Failure to make volume on boc!. Abort..

That is strange, 103 is VNOVOL, the error that the server returns when
the volume doesn't exist, but... you are trying to create it.

> 15:04:38 VLDBLookup: VLDB_size unset. Calling VCheckVLDB()
> 15:04:38 VCheckVLDB:  could not open VLDB
> 15:04:38 VLDBLookup: No or bad vldb.
> 15:04:53 VLDBLookup: VLDB_size unset. Calling VCheckVLDB()

That's a result of the client trying to get to the rootvolume.

> --and so on, with the last three messages repeating several times,
> ending with this message:
> 
> 15:08:54 VGetPartition Couldn't find partition /vicepa/
> 15:08:54 VCreateVolume: Cannot find partition /vicepa/. Bailing out.

Ah now I see the problem, it is probably the trailing slash on the
createvol_rep .... /vicepa/ that kills it. It can't figure out where to
put the volume.

Let's try to get rid of the volume on the server first:

    volutil purge 0x7F000006 coda_root
    > /vice/vol/VRList		# clean out the VRList

Then re-create the root volume:
    createvol_rep coda_root E0000100 /vicepa

Jan