Thank you guys, I really appreciate your help...
As you say, I better send you all the info so you will have a clear view
of what is happening.
Thanks again and sorry because this message is a little long!
Regards,

Below, my configuration:

Coda server and client correctly installed.
Server side:
# vice-setup
Do you want the file /usr/local/etc/coda/server.conf created? [yes]
What is the root directory for your coda server(s)? [/vice]
Is this the master server, aka the SCM machine? (y/n) y
serverid: 1
Setting up ROOTVOLUME file
Enter the name of the rootvolume (< 32 chars) : volumen
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: 507
Enter the username of this user: admin
Are you ready to set up RVM? [yes/no] yes
What is your log partition? (in this case, and don't have free partitions,
so I use
                             directories) /home/coda/log
What is your data partition (or file)? /home/coda/data
RVM setup is done!
Where shall we store your file data [/vicepa]? return
Shall I set up a vicetab entry for /vicepa (y/n) y
Server directory /vicepa is set up!

Then, I run:
# auth2 [ok]
# rpc2portmap [ok]
# updatesrv [ok]
# updateclnt -h server1 [ok]
Creating /vice/spool
# startserver & [ok]
# codasrv [ok]

I make a new volume:
# createvol_rep lucas E0000100
Getting initial version of /vice/vol/BigVolumeList.
V_BindToServer: binding to host server1.domain.com
GetVolumeList finished successfully
V_BindToServer: binding to host server1.domain.com
Servers are (server1 )
HexGroupId is 7f000000
creating volume lucas.0 on server1 (partition /vicepa)
V_BindToServer: binding to host server1.domain.com
V_BindToServer: binding to host server1.domain.com
Set Log parameters
Fetching volume lists from servers:
V_BindToServer: binding to host server1.domain.com
GetVolumeList finished successfully
 server1 - success
V_BindToServer: binding to host server1
VLDB completed.
<echo lucas 7f000000       1 1000001 0 0 0 0 0 0 0 E0000100 >>
/vice/db/VRList.new>
V_BindToServer: binding to host server1
VRDB completed.
Do you wish this volume to be Backed Up (y/n)? [n] y
Day to take full dumps: [Mon]
echoing 7f000000        IFIIIII        lucas >>/vice/db/dumplist

Client side:
venus-setup server1.domain1.com 100000
/etc/services already has new services registered! Good.
/etc/services ready for Coda
# venus

Date: Tue 11/18/2003

11:20:40 Coda Venus, version 6.0.3

11:20:40 /usr/coda/LOG size is 2692986 bytes
11:20:40 /usr/coda/DATA size is 10771944 bytes
11:20:40 Initializing RVM data...
11:20:40 ...done
11:20:40 Loading RVM data
11:20:40 Starting RealmDB scan
11:20:40        Found 1 realms
11:20:40 starting VDB scan
11:20:40        0 volume replicas
11:20:40        0 replicated volumes
11:20:40        0 CML entries allocated
11:20:40        0 CML entries on free-list
11:20:40 starting FSDB scan (4166, 100000) (25, 75, 4)
11:20:40        0 cache files in table (0 blocks)
11:20:40        4166 cache files on free-list
11:20:41 starting HDB scan
11:20:41        0 hdb entries in table
11:20:41        0 hdb entries on free-list
11:20:41 Initial LRDB allocation
11:20:41 Mounting root volume...
11:20:41 Venus starting...
11:20:41 /coda now mounted.

# mount
coda on /coda type coda (rw)

# ll
dr-xr-xr-x    2 root     65534        2048 nov 18 11:20 coda

# cfs mkm /coda/server1.domain.com/lucas lucas
/coda/server1.domain.com: No such file or directory

# ll -a /coda/server1.domain.com
lrw-r--r--    1 root     65534          34 nov 18 11:29
/coda/server1.domain.com -> #@server1.domain.com [in red]



>>>>>> "lucas" == lucas  <lucas_at_universogratis.com.ar> writes:
>
>     lucas> Good point, but no, there's no venus process running....
>
> There doesn't need to be a venus process running.  The problem is that
> on Linux process exit does not unmount the coda file system.  This
> means that if you shut down without an explicit umount, either by hand
> or from a shutdown script, the file system will remain mounted
> although it is useless.
>
> Try `mount' with no arguments.
>
> If you had done any work with the filesystem in any process still
> running, you may have CWDs pointing to it.  You need to either change
> CWD or kill those processes to unmount /coda.  I use
>
> ls -l /proc/[0-9]*/cwd | fgrep /coda
>
> as root to find them; other people use fuser, I think.
>
>> On Mon, 17 Nov 2003, Lucas wrote:
>>
>>> 14:01:39 Mounting root volume...
>>> 14:01:39 CHILD: mount system call failed. Killing parent.
>>
>> Is it, by any chance, a repeated venus startup?
>> Then you might have to manually umount /coda before you can run venus
>> again.
>>
>> Just a guess,
>> --
>> Ivan
>>
>>
>
>
>
> --
> Institute of Policy and Planning Sciences
> http://turnbull.sk.tsukuba.ac.jp
> University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573
> JAPAN
>                Ask not how you can "do" free software business;
>               ask what your business can "do for" free software.
>