From: Nix <nix@esperi.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Upgrade to 2.6.24 breaks NFS service
Date: Wed, 13 Feb 2008 08:58:03 +0000 [thread overview]
Message-ID: <87lk5pjkro.fsf@hades.wkstn.nix> (raw)
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 monitor esperi
Feb 12 22:53:45 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:53:45 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:54:20 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:54:20 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:54:55 loki notice: kernel: statd: server localhost not responding, timed out
Feb 12 22:54:55 loki notice: kernel: lockd: cannot monitor esperi
Feb 12 22:55:20 esperi notice: kernel: lockd: server loki.wkstn.nix not responding, still trying
(esperi is a UML instance on the same machine, connected via a bridged
TUN/TAP interface: the bridge, and network service to esperi and to the
rest of the local net across that bridge, was fine.)
I'm currently using NFSv3 atop nfs-utils 1.1.0.33-gdd08789, with daemons
being started in the suggested order (portmap, mountd, statd
--no-notify, nfsd). This evening I'm going to try to upgrade to
nfs-utils HEAD and see if this continues.
--
`The rest is a tale of post and counter-post.' --- Ian Rawlings
describes USENET
next reply other threads:[~2008-02-13 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:58 Nix [this message]
2008-02-13 10:19 ` Upgrade to 2.6.24 breaks NFS service Andrew Morton
2008-02-13 12:57 ` Jeff Layton
2008-02-14 0:14 ` Nix
2008-02-13 14:15 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lk5pjkro.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox