Coda File System

Re: newbie question 1

From: Jan Harkes <>
Date: Tue, 17 Jul 2001 07:50:20 -0400
On Tue, Jul 17, 2001 at 04:27:03AM +0800, tin wrote:
> hi all:
> May I know which Step is right ? (for setup coda server)
> 1(SCM)
> 1.create a mount point ext2 for vicepa
> 2.create a two partition for log and RVM
> vice-setup
> 4.start auth2
> 5.start rpc2
I guess this should be rpc2portmap/updatesrv/updateclnt.

Next, you would typically want to have the configuration done before you
actually start the Coda server. Most of the files are read only during
startup and you want both servers to come up with the right information.

> 7.modify /vice/db/servers  add the secondary server name and number in it
> 8.modify /vice/db/VSGDB add the secondary server name in it
> 6.start codasrv

> (secondary coda server)
> 9.create a mount point ext2 for vicepa
> 10. create two partitaion for log and RVM
> vice-setup

Run vice-setup for the non-scm case, it will use updatefetch and
updateclnt to pull in copies of the necessary configuration files from
updatesrv on the SCM. You might have to edit vicetab on the SCM to also

<new_server_name> /vicepa ftree width=64,depth=3

and 'touch /vicepa/FTREEDB' on the new server to allow it to recognise
and start using the /vicepa partition.

> 12.start auth2
> 13.start rpc2

I believe the non-scm server only needs the updateclnt daemon.

> 14.start codasrv

> (SCM)
> 15. createvolrep rootvolume E0000100 /vicepa
> (i tried this before seen is work but i dont know how to add additional coda
> server in E0000100 group when after createvolrep)

Yeah, working on that part. It is kind of tricky because a lot of
replication things are hanging off the VSG's which are assumed to be
fixed for the lifetime of the servergroup.

Right now, when adding a new server to an existing setup, the best
solution is to simply create a new server entry and new VSGDB entries
for the replication groups. Then restart all servers, and create new
volumes for the new VSG. Maybe it hadn't rung a bell yet, but VSGDB
stands for VSG database, it describes all know groups of server that can
potentially hold replicated volumes, i.e. volume storage groups.

Received on 2001-07-17 07:50:41