[OpenAFS] /afs directory not updated on client-side, Debian sid

Michael Janssen (CS/MATH stud.) janssen@student.cns.uni.edu
Wed, 1 May 2002 18:31:53 -0500


In Derek Atkins's email, 01-05-2002:
> This seems to imply that root.afs doesn't exist in your cell,
> or your client could not find it, or your AFS server is down.
> 
> You need to get your AFS Server running before you start your
> clients.
> 
> -derek
> 
> Michael Janssen (CS/MATH stud.) <janssen@henon.cns.uni.edu> writes:
> 
> > In Derek Atkins's email, 01-05-2002:
> > > Did you try running a few cache manager checks on your client:
> > >         fs checkb
> > >         fs checkv
> > > 
> > > -derek
> > 
> > When I got in today, I tried to do just that, but now I find that
> > openafs-client can't even mount AFS when the machines are started
> > again.  I had to hard-reboot the server due to some APM problems, I
> > suspect, this morning.  
> > 
> > The client has similar issues on a non-server machine.  
> > I get 
> > afsd: Can't mount AFS on /afs(22)
> > 
> > and when I try to stop the client (via 
> > /etc/init.d/openafs-client stop)  I get a kernel panic :(

Sorry, that was a DOH! moment.  I hadn't mounted /vicepa on boot.  I
seem to have the same problem on client and server now. 

In /afs/.myserver/: 
served1  served2  service  user

In /afs/myserver/:
service  user

`fs checkv` and `fs checkb` both print (on both client and server):
All volumeID/name mappings checked.

I can still read and write to /afs/.myserver/served[12] on both client
and server sides, and fs lsmount /afs/.myserver/served[12] returns
correctly in both places as well.

-- 
Michael Janssen -- Jamuraa -- janssen@cns.uni.edu -- jamuraa@base0.net  
GPG KEY 0xc00e9159  ---  http://www.base0.net  ---  jamuraa@debian.org
"The most overlooked  advantage of  owning a  computer is that if they 
foul up  there's  no law against  whacking them  around  a bit." -- EP