On Sat, 2012-03-31 at 13:55 +0200, Christoph Bartoschek wrote:
> Hi,
>
> we use Ubuntu 10.04.3 LTS and often get a traceback for NFS indicating that
> the daemon hangs for several seconds. At the same time some client machines
> cannot access the server and have to wait. After some minutes everything
> goes on.
>
> What could cause the problem? Is there anything we should change?
>
> Here is the message in the kernel log:
>
> [330573.697121] INFO: task nfsd:1376 blocked for more than 120 seconds.
> [330573.708375] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
> this message.
> [330573.730773] nfsd D 0000000000000001 0 1376 2
> 0x00000000
> [330573.730776] ffff88061c21bdc0 0000000000000046 0000000000015f00
> 0000000000015f00
> [330573.730779] ffff88061c111ad0 ffff88061c21bfd8 0000000000015f00
> ffff88061c111700
> [330573.730781] 0000000000015f00 ffff88061c21bfd8 0000000000015f00
> ffff88061c111ad0
> [330573.730784] Call Trace:
> [330573.730788] [<ffffffff81559e67>] __mutex_lock_slowpath+0x107/0x190
> [330573.730796] [<ffffffffa012300f>] ? svc_authorise+0x3f/0x50 [sunrpc]
At a guess, I'd say that your mountd or rpc.svcgssd is probably
busy/hanging, causing the kernel NFS daemon to hang while it waits to
authorise a client or user. Typically, you will see the above in the
case of a kerberos, NIS or ldap outage.
So are you using NIS or ldap-based netgroups in your /etc/exports, or
are your clients perhaps mounting with sys=krb5?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
