2011/08/17 08:27:25|Call Trace:
2011/08/17 08:27:25|[<ffffffff80235004>] warn_on_slowpath+0x64/0xa0
2011/08/17 08:27:25|[<ffffffff8024df06>] up+0x16/0x50
2011/08/17 08:27:25|[<ffffffff80235a35>] release_console_sem+0x1b5/0x1f0
2011/08/17 08:27:25|[<ffffffff805d9908>] lock_sock_nested+0xc8/0xe0
2011/08/17 08:27:25|[<ffffffff805d9908>] lock_sock_nested+0xc8/0xe0
2011/08/17 08:27:25|[<ffffffff806955c5>] schedule_timeout+0x95/0xd0
2011/08/17 08:27:25|[<ffffffff8062e1c2>] inet_sock_destruct+0x172/0x1c0
2011/08/17 08:27:25|[<ffffffff805d9f83>] sk_free+0x23/0x110
2011/08/17 08:27:25|[<ffffffff8062d9be>] inet_release+0x3e/0x70
2011/08/17 08:27:25|[<ffffffff805d7131>] sock_release+0x21/0x90
2011/08/17 08:27:25|[<ffffffff805d771e>] sock_close+0x1e/0x40
2011/08/17 08:27:25|[<ffffffff80296eb1>] __fput+0xb1/0x1d0
2011/08/17 08:27:25|[<ffffffff80664ae2>] svc_sock_free+0x22/0x60
2011/08/17 08:27:25|[<ffffffff8066f228>] svc_xprt_free+0x38/0x50
2011/08/17 08:27:25|[<ffffffff8066f1f0>] svc_xprt_free+0x0/0x50
2011/08/17 08:27:25|[<ffffffff8041f443>] kref_put+0x33/0x70
2011/08/17 08:27:25|[<ffffffff8066fa57>] svc_close_all+0x57/0x70
2011/08/17 08:27:25|[<ffffffff806638be>] svc_destroy+0x5e/0x150
2011/08/17 08:27:25|[<ffffffff8034ac0e>] nfsd+0x26e/0x2a0
2011/08/17 08:27:25|[<ffffffff8034a9a0>] nfsd+0x0/0x2a0
2011/08/17 08:27:25|[<ffffffff802499ab>] kthread+0x4b/0x80
2011/08/17 08:27:25|[<ffffffff8020d149>] child_rip+0xa/0x11
2011/08/17 08:27:25|[<ffffffff80249960>] kthread+0x0/0x80
2011/08/17 08:27:25|[<ffffffff8020d13f>] child_rip+0x0/0x11
This may indicate a stale NFS mount.
To correct it, the hosts need to re-mount the NFS share after storage reboots.
I think this is a known issue with NFS.