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

2011-04-01 Thread Dirk Heinrichs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 27.03.2011 01:42, schrieb Russ Allbery: Dirk Heinrichs dirk.heinri...@altum.de 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,

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

2011-04-01 Thread Russ Allbery
Dirk Heinrichs dirk.heinri...@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

[OpenAFS] afs: Waiting for busy volume 0

2011-03-26 Thread Dirk Heinrichs
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

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

2011-03-26 Thread Derrick Brashear
: 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

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

2011-03-26 Thread 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

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

2011-03-26 Thread Derrick Brashear
'is too!' echo t /proc/sysrq-trigger Derrick On Mar 26, 2011, at 1:06 PM, Dirk Heinrichs dirk.heinri...@altum.de 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

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

2011-03-26 Thread 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:

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

2011-03-26 Thread 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

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

2011-03-26 Thread Russ Allbery
Dirk Heinrichs dirk.heinri...@altum.de 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