[OpenAFS-devel] Problems with shutting down afsd - revisited

[Markus Alt]

Derrick J Brashear wrote:
> 
> On Sun, 27 May 2001, Markus Alt wrote:
> 
> > I haven't tried it so far, but I can imagine at least two problems with
> > that:
> >
> > 1. If I leave AFS running although I shut the network down and reconnect
> > the machine the next morning, how long will it take until the AFS client
> > recovers? And will it recover at all after such a "long" period of
> > network outage?
> 
> My laptop has a 1.0.4 client pointed at the 1.0.4 server in my house. I
> walk off the network, then come back hours later, rejoin the network, says
> fs checks, and I'm back in business.

As all of you suggest this, I will try and see how it works. I'll keep
you posted.

> > 2. More severe: As I usually also have AFS directories in my $PATH,
> > would working with a still running AFS client but no network connection
> > be possible? In other words: Wouldn't I get quite long, annoying
> > timeouts each time I e.g. try to expand a file or command name in the
> > shell (as it also tries to look into the AFS dirs)?
> >
> > That's why I'd rather have a "clean" solution like I had with kernel 2.2
> > - or disconnected AFS! Ah, what did you say, when it will be ready ...?
> > ;-)
> 
> What exactly broke between 2.2 and 2.4? Nothing did from my perspective;
> What am I not doing that you are?

Good question! That's exactly what I want to know. ;-)

Another thing I've been observing: If I shut down AFS a short time (say
10 minutes) after it has been started, there's usually no problem. If I
use it for a longer period and use it heavily, thus the cache gets
filled up, the shutdown doesn't work. This led me to the conclusion that
my problem seems to be somewhat related to the amount of non-empty cache
entries.

I've tried the following: Delete all the V* files in /usr/vice/cache
each time before starting the AFS client. And indeed, I haven't had
problems when shutting AFS down again since then - at least so far! (Of
course, this really minimizes the benefit of the cache, as it only
contains stuff that was cached since the last startup of AFS.)

In addition to that, since my upgrade to  2.4, I've always had (and
still have) an error message saying that unmounting /usr/vice/cache at
machine shutdown was not possible, as the device was busy. (Only if the
AFS client was used before, of course.) This happens regardless whether
shutting down AFS was successful or not. Really strange, as there are no
more AFS related processes after a clean shutdown - at least this is
what "ps", "lsof" and "fuser" tell me.

Markus

-- 
Markus Alt
IBM Lab Boeblingen, Germany
altmark@de.ibm.com