Coda File System

problems with "createvol_rep"

From: Madhav <>
Date: Fri, 10 Mar 2000 18:12:44 +0530

Actually I had problems with creating rootvolume using the command
createvol_rep (not getting the proper hostname because of the entry in
/etc/hosts). And later as suggested I have edited that file to have the
name. Then also I got the same message
"RPC2_NewBinding to server server1 failed with RPC2_NOBINDING(F)
Failure to make volume on server1!. Abort.."
Then I reinstalled linux in the machine(server1) so that I can have
seperate partitions for vice,vicepa,RVMDATA and RVMLOG.
Even then I got the same message while trying to create rootvolume using

Can anbody please help me out. I am stuck here for the last two  days.


Sorry for all the junk I am putting here. But I am stuck here.
This is my vice-setup conversation.
[root_at_server1 /]# vice-setup
Setting up config files (under /vice).
Directories under /vice are set up.

Setting up tokens for authentication.
The following tokens must be identical on all servers.
Enter a random token for auth2 authentication : server01
The following tokens must be identical on all servers.
Enter a random token for volutil authentication : codavol1
tokens done!

Setting up the file list for update
filelist for update ready.

Populating /vice/vol...
lockfiles created.
/etc/services already has new services registered! Good.
/etc/services ready for Coda
Is this the master server, aka the SCM machine? (y/n) y
Now installing files specific to the SCM...

Setting up servers file.
Enter an id for this server.
The serverid should be a number between 0 and 255 *avoid 0, 127, and
serverid: 1
Initializing the VSGDB to contain the SCM as E0000100
/vice/db/VSGDB set up

Setting up ROOTVOLUME file
Enter the name of the rootvolume (< 32 chars) : rootvol

Setting up users and groups for Coda

You need to give me a uid (not 0) and username (not root)
for a Coda System:Administrator member on this server,
(sort of a Coda super user)

Enter the uid of this user: 1
Enter the username of this user: admin
Going to rebuild the protection databases
moving /vice/db/prot_users.db to /vice/db/prot_users.db.old
moving /vice/db/prot_index.db to /vice/db/prot_index.db.old
An initial administrative user admin (id 1)
with Coda password changeme now exists.

You need a small log disk partition, preferrably on a disk by itself.
You need a metadata partition of approx 4% of you filespace.

For trial purposes you may give oridnary files instead of raw
partitions. Keep all size small if you do this.
Production servers will want partitions for speed.

WARNING: you are going to play with your partitions now.
verify all answers you give.

WARNING: these choices are not easy to change once you are up and running.

Are you ready to set up RVM? [yes/no] yes

What is your log partition? /dev/hda12

The log size must be smaller than you log partition.
We recommend not more than 30M log size, and 2M is a good choice.
What is your log size? (enter as e.g. '2M') 12M

What is your data partition (or file)? /dev/hda11

The data size must be approx 4% of you server file space.
We have templates for servers of approx: 500M, 1G, 2.2G, 3.3G, 8G
(you can store less, but not more on such servers).
The corresponding data sizes are  22M, 44M, 90M, 130M, 315M.
(use 315M only on very fast machines)
Pick one of the defaults, otherwise I will bail out

What is the size of you data partition (or file)
[22M,44M, 90M, 130M, 200M, 315M]: 133M

WARNING: DATA and LOG partitions are about to be wiped.

  --- log area: /dev/hda12, size 12M.
  --- data area: /dev/hda11, size 133M.

Proceed, and wipe out old data? [y/n] y

LOG file has been initialized!

Read rdsinit(8) use rdsinit to configure your data area.

Your server directories will hold the files (not directories).
You can currently only have one directory per disk partition.

Where shall we store your data [/vicepa]? /vicepa
Shall I set up a vicetab entry for approx 256000 files for /vicepa (y/n) y
Now initializing the partition. This takes a while....
Partition /vicepa: inodes in use: 0, total: 262144.

Date: Fri 03/10/2000

17:14:18 Partition /vicepa: 382720K available (minfree=5%), 382715K free.
Server directory is set up!

Congratulations: your configuration is ready...and now
to get going do the following:
 - start the auth2 server as: auth2
 - start rpc2portmap as: rpc2portmap
 - start updateclnt as:  updateclnt -h server1 -q coda_udpsrv
 - start updatesrv as: updatesrv -p /vice/db
 - start the fileserver: startserver &
 - wait until the server is up: tail -f /vice/srv/SrvLog
 - create your root volume: createvol_rep rootvol E0000100 /vicepa
 - setup a client: venus-setup server1 20000
 - start venus: venus
 - enjoy Coda.
[root_at_server1 /]#/etc/rc.d/init.d/update.init.start
[root_at_server1 /]#/etc/rc.d/init.d/auth2.init start
[root_at_server1 /]#/etc/rc.d/init.d/codasrv.init start
[root_at_server1 /root]# createvol_rep rootvolume E0000100 /vicepa
Servers are (server1 )
HexGroupId is 7F000000
creating volume rootvolume.0 on server1
V_BindToServer: binding to host sever1
RPC2_NewBinding to server sever1 failed with RPC2_NOBINDING (F)
Failure to make volume on server1!. Abort..
[root_at_server1 /root]#
Received on 2000-03-10 07:55:51