From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jonathan Steinert <hachi-rIxVFxJalAJeoWH0uzbU5w@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsd rpc service update failures on 2.6.32
Date: Wed, 20 Oct 2010 12:59:10 -0400 [thread overview]
Message-ID: <20101020165909.GB2804@fieldses.org> (raw)
In-Reply-To: <20101017142918.GA6805@miyako>
On Sun, Oct 17, 2010 at 07:29:19AM -0700, Jonathan Steinert wrote:
> Hi folks, I've got a machine here that I've been debugging NFS issues on for a week or so now.
>
> I've boiled the issue down to this:
>
> Start up the NFS server, this seems to work fine, no errors:
> rpc.nfsd 1
>
> Check to see if nfsd has registered with rpcbind, this never shows the nfsd service being registered:
> rpcinfo -p
>
> So far I've got the following diagnostics done:
>
> - Cranked up the debugging in rpcbind, never found SET updates happening (only UNSET)
> - Captured the rpc update frames going over lo, viewed in wireshark. They are all UNSET only
> - Crank up rpcdebug on kernel, only unregister frames are being generated.
>
> The interesting thing I see is:
>
> svc: svc_register(nfsdv4, udp, 0, 2)
> RPC: unregistering [100003, 4, 0.0.0.0.0.0, 'udp'] with local rpcbind
>
> For some reason svc_register is being called with '0' as the port argument.
>
> Looking at the ports list in proc says that udp and tcp 2049 are to be used.
>
> I've been searching around for any information regarding this issue, but haven't found anything. Do any of you folks know if this has been fixed in a later kernel? Is this even a known issue of some kind? I would be testing a newer kernel, but my box has a major issue with some driver as of 2.6.33, which I am also still debugging.
>
> Not subscribed to this list, please CC me if you can. I'll watch the archives too.
It doesn't ring any bells. What distro are you using, and how is it
starting nfsd?
--b.
prev parent reply other threads:[~2010-10-20 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 14:29 nfsd rpc service update failures on 2.6.32 Jonathan Steinert
2010-10-20 16:59 ` J. Bruce Fields [this message]
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=20101020165909.GB2804@fieldses.org \
--to=bfields@fieldses.org \
--cc=hachi-rIxVFxJalAJeoWH0uzbU5w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).