[OpenAFS] afs: Waiting for busy volume 0

Russ Allbery rra@stanford.edu
Fri, 01 Apr 2011 14:42:11 -0700

Dirk Heinrichs <dirk.heinrichs@altum.de> writes:
> Am 27.03.2011 01:42, schrieb Russ Allbery:

>> In the openafs-client init script, add openafs-fileserver to the end of
>> the Should-Start configuration line in the header and add a Should-Stop
>> line like:

>> # Should-Stop:          openafs-fileserver

>> Sorry about that.  I'll fix that in the next release.

I should have mentioned that you have to run insserv after doing this to
change the symlink values.

> Found some time today to reboot that box and the problem has
> disappeared. However, I don't think it's related to init script
> ordering. IMHO they should be completely independant, since one can run
> the server on one box and the client on another, or am I completely
> wrong, here?

They can, but what the above is saying is "if there's a file server on
this box as well, start the client after the file server and stop the
client before the file server."  If there isn't a file server on the same
host, the Should-* bits are ignored.  So it catches the case where the
client wants to break callbacks or read files from the file server on the
same host.

Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>