The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Jeff Layton <jlayton@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: Upgrade to 2.6.24 breaks NFS service
Date: Thu, 14 Feb 2008 00:14:50 +0000	[thread overview]
Message-ID: <878x1ojsw5.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20080213075738.086f7b32@barsoom.rdu.redhat.com> (Jeff Layton's message of "Wed, 13 Feb 2008 07:57:38 -0500")

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 that it doesn't necessarily do so. That may be the
> problem here.

I rebooted back into 2.6.24.2 again, and everything works now, without
even upgrading nfs-utils (although I did that anyway, to nfs-utils git
head, and it's still happy).

Linux: debugs itself, no human intervention required! :)



(The inconsistency of this screams `port allocation' to me. If it
happens again I'll get some rpcinfo output and packet dumps. I'd
have done it this time if it hadn't been for the plug-the-security-
hole rush and it being 2am.)

-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET

  reply	other threads:[~2008-02-14  0:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  8:58 Upgrade to 2.6.24 breaks NFS service Nix
2008-02-13 10:19 ` Andrew Morton
2008-02-13 12:57   ` Jeff Layton
2008-02-14  0:14     ` Nix [this message]
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=878x1ojsw5.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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