On 13 Feb 2008, Jeff Layton told this:
> If upgrading nfs-utils doesn't help, on this box, could you run:
>
> # rpcinfo -p localhost
>
> send the output? statd expects that lockd will always be listening on a
> UDP socket and some changes recently made it so that when there are
> only TCP mounts t
On Wed, 2008-02-13 at 08:58 +, Nix wrote:
> I upgraded from 2.6.23.10 to 2.6.24.2 yesterday, and found NFS service
> failing.
>
> To be specific, all locks were blocking forever, with an endless flood
> of
>
> Feb 12 22:53:10 loki notice: kernel: statd: server localhost not responding,
> ti
On Wed, 13 Feb 2008 02:19:12 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> (cc linux-nfs)
>
> On Wed, 13 Feb 2008 08:58:03 + Nix <[EMAIL PROTECTED]> wrote:
>
> > I upgraded from 2.6.23.10 to 2.6.24.2 yesterday, and found NFS
> > service failing.
> >
> > To be specific, all locks were blo
(cc linux-nfs)
On Wed, 13 Feb 2008 08:58:03 + Nix <[EMAIL PROTECTED]> wrote:
> I upgraded from 2.6.23.10 to 2.6.24.2 yesterday, and found NFS service
> failing.
>
> To be specific, all locks were blocking forever, with an endless flood
> of
>
> Feb 12 22:53:10 loki notice: kernel: statd: se
I upgraded from 2.6.23.10 to 2.6.24.2 yesterday, and found NFS service
failing.
To be specific, all locks were blocking forever, with an endless flood
of
Feb 12 22:53:10 loki notice: kernel: statd: server localhost not responding,
timed out
Feb 12 22:53:10 loki notice: kernel: lockd: cannot moni
5 matches
Mail list logo
