On Mon, Sep 02, 2002 at 12:06:19PM -0700, R. Church wrote:
> This looks like useful information. This is what I have in my syslog
> on the client that fails to mount /coda:
> 
> coda_read_super: device index: 0
> coda_read_super: rootfid is (0x7f000001,0x1,0x1)
> Failure of coda_cnode_make for root: error -110

ETIMEDOUT. Your laptop is unable to talk to the server, and as such it
is unable to get the required information for the root inode (/coda)
which the kernel needs to finish the mount process.

Is there anything in venus.log, if you are using the Debian package it
is probably in /var/log/coda/, otherwise it is in /usr/coda/etc/

Other simple tasts, can you ping the server's ip-address. I believe
5.3.19 also included a couple of small programs to help debug these
kinds of things.

rpc2ping <servername>

    Tries to set up an RPC2 connection to the Coda server and exits.

getvolinfo <servername> <volumename>

    Sets up an RPC2 connection to the server and requests information
    about the specified volume. You can then use this information to see
    whether the returned ip-addresses are reachable. This comes pretty
    close to what venus does around the time the mount is failing in
    your case.

Jan