Coda File System

Re: Coda server on Debian

From: Jan Harkes <jaharkes_at_cs.cmu.edu>
Date: Sun, 23 Mar 2003 15:35:43 -0500
On Sun, Mar 23, 2003 at 09:02:18PM +0100, Peter Schuller wrote:
> V_BindToServer: binding to host equinox.infidyne.com
> P/vicepa Hequinox T22e5df8 F182f4c
> Wcoda:root.0 I1000001 H1 P/vicepa m0 M0 U2 W1000001 C3e7ddb42 D3e7ddb42
> B0 A0
> GetVolumeList finished successfully
> 
> It doesn't seem to honor the changes I made manually though (equinox
> rather than equinox.infidyne.com).

That might not be a problem as long as equinox resolves to the same
address as equinox.infidyne.com.

> >     'getvolinfo <servername> <rootvolname>'
> >     'getvolinfo <servername> <rootvolname>.0'
> >     'getvolinfo <servername> <root volumeid>'
> >     'getvolinfo <servername> <replica volumeid>'
> 
> This all seems to work. Both from the server in question, and from one
> of the clients that can't connect with the Coda client (the NetBSD box).

I guess it has the correct IP address for equinox where it says
Replica0 id <foo>, Server0 <ipaddress>

As all of these check out correctly, your server setup should just work.
The only thing I can think of now is that it is a client problem.o

Do all servers listed as rootserver in /etc/coda/venus.conf give the
same correct results to getvolinfo queries? It could be that the client
is still trying to talk to your old server. Perhaps an RVM
reinitialization will bring it into submission,

    # make sure no shells or processes have references in /coda so that
    # we can umount...
    vutil shutdown
    umount /coda
    venus -init &

Jan
Received on 2003-03-23 15:36:55