Linux NFS development
 help / color / mirror / Atom feed
From: "Hans-Peter Jansen" <hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine
Date: Wed, 15 Apr 2009 15:48:11 +0200	[thread overview]
Message-ID: <200904151548.12291.hpj@urpla.net> (raw)
In-Reply-To: <1239799114.5177.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

Am Mittwoch, 15. April 2009 schrieb Trond Myklebust:
> On Wed, 2009-04-15 at 12:50 +0200, Hans-Peter Jansen wrote:
> > Hi,
> >
> > I suffer from a problem, where my diskless environment doesn't work
> > anymore after upgrading the server from openSUSE 11.0 (2.6.25.20) to
> > openSUSE 11.1 (2.6.27.21).
> >
> > The diskless environment gets set up with an customized initrd via
> > pxelinux. The initrd uses klibc's nfsmount, and I've tried both
> > protocols: udp and tcp. It's not an iptables issue, since I can mount
> > these directories from other (fully booted) systems just fine.
> >
> > Using the debug version of klibc's nfsmount prints these messages:
> > short read: 0 < 28
> > Port for 100003/3[udp]: 0
> > short read: 0 < 28
> > Port for 100005/3[udp]: 0
> > NFS params:
> >   server = xxx.xx.xx.xx, path = "/roroot", version = 3, proto = udp,
> >   mount_port = 627, nfs_port = 2049, flags = 00010282,
>
>     ^^^^^^^^^^^^^^^^
>
> >   rsize = 0, wsize = 0, timeo = 7, retrans = 3,
> >   acreg (min,max) = (3,60), acdir (min,max) = (30,60),
> >   soft = 0, intr = 1, posix = 0, nocto = 0, noac = 0
> >
> > tcpdumping the communication shows, that for whatever reason, the
> > client sends the mount request from source port 798 to destination port
> > 627, but the server doesn't listen on 627:
>
> The question is why is klibc specifying mount port = 627?

Well, this is exactly my problem. That's the mount port, but this one cannot 
be set to a manual value, thus the rpc stuff infront of it must have gone 
wrong.

[Update]
Issue solved. It was that silly rpcbind package (0.1.6+git20080930-5.2), 
that has gone wrong. Replacing it with portmap (6.0+git20070716-31.37) did 
it. Looks like this deserves a new bugzilla record.

Sorry for the churn and thanks for your care, Trond.

Pete

  parent reply	other threads:[~2009-04-15 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 10:50 klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine 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 [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2009-04-15 19:17 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

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=200904151548.12291.hpj@urpla.net \
    --to=hpj-2x7n3sizjbfeowh0uzbu5w@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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