Coda File System

installation confusion

From: Jeff Breidenbach <jeff_at_jab.org>
Date: Thu, 10 Sep 1998 20:57:55 -0400
Suggestions appreciated...

I got further, fixing my eth0 interface, but still no success. I
didn't get the SCM running correctly after all; a problem comes up in
the createvol command. I'm hoping that I'm just running the wrong
command. The shell script's printed instructions and the HTML docs
disagree on what to type.

Platform: i386 linux
Distribution: today's Redhat Rawhide
Coda installation method: RPM
Coda version: 4.6.5
Kernel: 2.1.120 

Thank you,
Jeff

------------------------------------------------------------------

[root_at_marmot /]# 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 : elephant
The following tokens must be identical on all servers.
Enter a random token for volutil authentication : elephant
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 (a number > 0 < 255) : 1
done!
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) : jab
done!

** When srv, updatesrv and updateclnt are running, 
** and you have a data partition PART (such as /vicepa) issue 
** the command createvol jab  scm-hostname PART

Setting up users and groups for Coda
1 user entries found
An initial administrative user "admin" with passwod "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/hdc7

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. '12M') 12M

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

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 330M 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,
315M]: 44M

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

  --- log area: /dev/hdc7, size 12M.
  --- data area: /dev/hdc6, size 44M.

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


LOG file has been initialized!


Rdsinit will initialize data and log.
This takes a while.
rvm_initialize succeeded.
Going to initialize data file to zero, could take awhile.
done.
Just mapped in region (20000000,37748736)
Just mapped in region (22400000,1048576)
rds_zap_heap completed successfully.
rvm_terminate succeeded.
RVM setup is done!


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]? 
mkdir: cannot make directory `/vicepa': File exists
Shall I set up a vicetab entry for approx 256000 files for /vicepa
(y/n) y
grep: /vice/db/vicetab: No such file or directory
Now initializing the partition. This takes a while....
Partition /vicepa: inodes in use: 0, total: 262144.

Date: Thu 09/10/98

21:27:01 Partition /vicepa: 3191494 available size (1K blocks,
minfree=5%), 3191493 free blocks.
done.
Server directory is set up!

[root_at_marmot /]# /etc/rc.d/init.d/update.init start
rpc2portmap
updatesrv
updateclnt
Creating /vice/spool

[root_at_marmot /]# /etc/rc.d/init.d/auth2.init start
/usr/sbin/auth2

[root_at_marmot /]# createvol_rep coda:jab E0000100 /vicepa
Servers are (marmot)
HexGroupId is 7F000000
creating volume coda:jab.0 on marmot
V_BindToServer: binding to host marmot.jab.org
RPC2_NewBinding to server marmot.jab.org failed with RPC2_NOBINDING
(F)
.: Event not found.
Received on 1998-09-10 21:58:29