From: "Hans-Peter Jansen" <hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine
Date: Wed, 15 Apr 2009 12:50:49 +0200 [thread overview]
Message-ID: <200904151250.49372.hpj@urpla.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
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:
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 41656 mountd
100005 1 tcp 49063 mountd
100005 2 udp 41656 mountd
100005 2 tcp 49063 mountd
100005 3 udp 41656 mountd
100005 3 tcp 49063 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 33144 nlockmgr
100021 3 udp 33144 nlockmgr
100021 4 udp 33144 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 57268 nlockmgr
100021 3 tcp 57268 nlockmgr
100021 4 tcp 57268 nlockmgr
100024 1 udp 39508 status
100024 1 tcp 45430 status
I've attached the relevant tcpdump section.
I would be very grateful, if some kind soul could enlight me here, as I'm
fully puzzled..
Pete
[-- Attachment #2: shark-nfs-mount.dump --]
[-- Type: application/octet-stream, Size: 4824 bytes --]
next reply other threads:[~2009-04-15 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 10:50 Hans-Peter Jansen [this message]
[not found] ` <200904151250.49372.hpj-2x7n3sizJbFeoWH0uzbU5w@public.gmane.org>
2009-04-15 12:38 ` klibc's nfsmount failure with 2.6.27.21, while 2.6.25.20 was fine 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
-- 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=200904151250.49372.hpj@urpla.net \
--to=hpj-2x7n3sizjbfeowh0uzbu5w@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