From: "Hans-Peter Jansen" <hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine
Date: Thu, 16 Apr 2009 00:48:46 +0200 [thread overview]
Message-ID: <200904160048.46625.hpj@urpla.net> (raw)
In-Reply-To: <889BAE90-0719-4560-B4D3-34376B0FFC4C@oracle.com>
Am Mittwoch, 15. April 2009 schrieb Chuck Lever:
> On Apr 15, 2009, at 3:17 PM, Hans-Peter Jansen wrote:
> >
> > =C4hem, Chuck, may I ask you to look into the initial mail again. T=
he
> > failing
> > case is attached there. Here I've attached the good one. Since I
> > couldn't
> > locate any mount attempt in the dump, I've left a few more nfs
> > transactions.
>
> The client makes a PMAP_GETPORT request via TCP. The server's rpcbin=
d
> drops the connection without replying after receiving the request. I
> didn't see anything immediately wrong with the request, although
> wireshark didn't like it either. I had to decode it by hand.
8[
> Restarting rpcbind usually means you lose all your rpc service
> registrations until you restart those services, but it would be worth
> trying this: stop the server's rpcbind service, then run rpcbind in a
> terminal session with "-d" to see what it thinks the problem is when
> it drops the connection.
>
> Please attach a copy of your /etc/netconfig to reply.
Okay, but since it requires yet another portmap <-> rpcbind swap, pleas=
e=20
give me a few days to find a appropriate slot.
Pete
next prev parent reply other threads:[~2009-04-15 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:17 klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine Hans-Peter Jansen
[not found] ` <200904152117.41367.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
2009-04-15 20:52 ` Chuck Lever
2009-04-15 22:48 ` Hans-Peter Jansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 10:50 Hans-Peter Jansen
[not found] ` <200904151250.49372.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
2009-04-15 12:38 ` Trond Myklebust
[not found] ` <1239799114.5177.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-15 13:48 ` Hans-Peter Jansen
[not found] ` <200904151548.12291.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
2009-04-15 14:36 ` Chuck Lever
2009-04-15 17:23 ` Hans-Peter Jansen
[not found] ` <200904151923.58709.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
2009-04-15 17:35 ` Chuck Lever
2009-04-15 19:16 ` Hans-Peter Jansen
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=200904160048.46625.hpj@urpla.net \
--to=hpj-2x7n3sizjbfeowh0uzbu5w@public.gmane.org \
--cc=chuck.lever@oracle.com \
--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