Re: [OpenAFS] afs: Waiting for busy volume 0

[Derrick Brashear]

alt-sysrq-t (assuming logging is still up at that point) would make it
much easier to discern what's up.


On Sat, Mar 26, 2011 at 4:00 AM, Dirk Heinrichs  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> On my Debian Squeeze system shutdown became really slow recently because
> of "afs: Waiting for busy volume 0" for several minutes, like:
>
> Stopping OpenAFS services.
> Stopping OpenAFS BOS server: bosserver.
> Stopping Postfix Mail Transport Agent: postfix.
> Stopping AFS services:afs: Lost contact with file server 192.168.1.1 in
> cell altum.de (all multi-homed ip addresses down for the server)
> afs: Lost contact with file server 192.168.1.1 in cell altum.de (all
> multi-homed ip addresses down for the server)
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> afs: Waiting for busy volume 0
> ...
>
> OpenAFS is 1.6pre3, kernel 2.6.38.1.
>
> Any hints what could be the cause for this?
>
> Thanks...
>
>        Dirk
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iD8DBQFNjZ0m8NVtnsLkZ7sRAm0nAKCgvMlnfwC/3f7f1El57n/ZW/hJBgCeKpz8
> +qdxTlZUndBZaQ7BTJPGfVc=
> =EIcw
> -END PGP SIGNATURE-
> ___
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>



-- 
Derrick
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Dirk Heinrichs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 26.03.2011 14:30, schrieb Derrick Brashear:

> alt-sysrq-t (assuming logging is still up at that point) would make
> it much easier to discern what's up.

It's a headless ARM system (GuruPlug), no alt-sysrq. The posted output
was captured by connecting via serial console.

Bye...

Dirk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNjhzm8NVtnsLkZ7sRArWvAJ40OWReqmV/vGcjSmbRwG93FBqFRQCgmB44
W+ZC93WGjoK8sIhrnPUCvJk=
=zJ5D
-END PGP SIGNATURE-
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Derrick Brashear]

'is too!'

echo t > /proc/sysrq-trigger

Derrick


On Mar 26, 2011, at 1:06 PM, Dirk Heinrichs  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Am 26.03.2011 14:30, schrieb Derrick Brashear:
> 
>> alt-sysrq-t (assuming logging is still up at that point) would make
>> it much easier to discern what's up.
> 
> It's a headless ARM system (GuruPlug), no alt-sysrq. The posted output
> was captured by connecting via serial console.
> 
> Bye...
> 
>Dirk
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iD8DBQFNjhzm8NVtnsLkZ7sRArWvAJ40OWReqmV/vGcjSmbRwG93FBqFRQCgmB44
> W+ZC93WGjoK8sIhrnPUCvJk=
> =zJ5D
> -END PGP SIGNATURE-
> ___
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Dirk Heinrichs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 26.03.2011 13:55, schrieb Rogier Krieger:

> It's merely a guess, but did your fileserver go into shutdown before
> your client/cache manager? I imagine you'd prefer things to go the
> other way around.

According to the output I've posted, yes:

Stopping OpenAFS services.
Stopping OpenAFS BOS server: bosserver.
Stopping Postfix Mail Transport Agent: postfix.
Stopping AFS services:afs: Lost contact with file server 192.168.1.1 in

>  Any changes in the order of your start/stop scripts?

No. They're both installed as K02* in /etc/rc6.d (default). So I guess
it's up to the init system how to order them.

Bye...

Dirk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNjjLr8NVtnsLkZ7sRAldaAJ9xvBybMAUWEOTLSnNYHcj+RNyvvgCfQANc
ZuKUPcd26mkfNiHfZkSBZ2A=
=gy9H
-END PGP SIGNATURE-
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Dirk Heinrichs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 26.03.2011 18:07, schrieb Derrick Brashear:

> echo t > /proc/sysrq-trigger

Ah, ok. But it seems I first need to recompile the kernel with SYSRQ
support enabled :(

Bye...

Dirk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNjjQU8NVtnsLkZ7sRAm5jAKCL2qZXil/A0DQLOpT9BbpW0Lj1WQCeOVKQ
EgZWV5lScoFgwrDeXZs4+N0=
=k2b4
-END PGP SIGNATURE-
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Russ Allbery]

Dirk Heinrichs  writes:

> No. They're both installed as K02* in /etc/rc6.d (default). So I guess
> it's up to the init system how to order them.

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.

-- 
Russ Allbery (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Dirk Heinrichs]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 27.03.2011 01:42, schrieb Russ Allbery:
> Dirk Heinrichs  writes:
> 
>> No. They're both installed as K02* in /etc/rc6.d (default). So I guess
>> it's up to the init system how to order them.
> 
> 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.

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?

Bye...

Dirk
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFNlkK78NVtnsLkZ7sRAiGTAJwNXSgKE0OiVUnBo8WO8W4uqrd+DACfcqgL
yrZsIkR+9du0tBV9obtW+2E=
=25LK
-END PGP SIGNATURE-
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] afs: Waiting for busy volume 0

[Russ Allbery]

Dirk Heinrichs  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 (r...@stanford.edu) 
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info