Your message dated Sun, 08 Aug 2010 23:02:09 +0000
with message-id <e1oiesb-0004ll...@franck.debian.org>
and subject line Bug#582003: fixed in nfs-utils 1:1.2.2-3
has caused the Debian Bug report #582003,
regarding nfs-common: nfs client ignores "port=2049" option when mounting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
582003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.2-1
Severity: normal
Tags: sid
Hi,
I'm trying to mount an NFS server that isn't registered in the portmapper. I
believe this has worked in the past and something changed moderately recently
(probably between 2009-11-19 and 2010-5-1) that broke this behaviour.
The options supplied to mount (via -o) are:
nfsvers=2,nolock,udp,noac,intr,rw,mountport=<mount>,port=2049
(where <mount> is the UDP port of the NFS mount daemon; the mount daemon isn't
bound to some well-known port, but is discovered by a support script)
An attempt to mount the NFS server using the above options fails. Watching the
network traffic, I see the following SunRPC calls:
1. SunRPC NULL call to a MOUNT service (running on UDP port <mount>) ... this
is successful
2. SunRPC MNT call to a MOUNT service (running on UDP port <mount>) ... this
is successful
3. SunRPC GETPORT call to Portmap service .. this is unsuccessful (no
registered program)
The failing GETPORT call to portmapper is querying for program 10000003 (NFS),
version 2, proto UDP. The failure of this call is expected: the NFS server
isn't registered in the portmapper service, so such a query should fail.
However, what isn't clear is why the client is calling the Portmapper service
since the port number has been supplied in the mount options ("port=2049")
What is interesting is if a different port value is specified (e.g.,
"port=2050") then the network interaction changes to:
1. SunRPC NULL call to a MOUNT service ... this is successful
2. SunRPC MNT call to a MOUNT service ... this is successful
3. SunRPC NULL call to UDP port 2050 ... this is unsuccessful (no reply)
Since there is no program listening on port 2050, the attempt to call NULL on
that port will have no reply (the mount will eventually time-out); however,
notice how no attempt is made to contact the Portmapper service to discover the
NFS daemon port.
I'd speculate that the problem here is that port=2049 is somehow used as a
place-holder value indicating that the NFS daemon port value is unknown. If
so, then the system will be unable to distinguish between a mount request with
options including "port=2049" and options without any "port" option. However,
the behaviour of the NFS client should be different: if port=2049 is specified
then the RPC portmapper lookup is unnecessary and should be avoided.
It's unclear to me whether the problem is in mount.nfs or with the Linux kernel
itself (fs/nfs). I've assigned it to nfs-common as an initial guess, but the
problem may lie in the kernel code.
NB, I'm running the Nouveau kernel, which is based on 2.6.32 whilst waiting for
2.6.33 (and the Nouveau DRM driver) to appear in sid. This NFS problem could
be an artifact of using this kernel; but I've scanned the changelog of the
2.6.32 kernels and there doesn't seem to be a fix for this issue mentioned.
Cheers,
Paul.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-20100317 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nfs-common depends on:
ii adduser 3.112 add and remove users and groups
ii initscripts 2.87dsf-10 scripts for initializing and shutt
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcap2 1:2.17-2 support for getting/setting POSIX.
ii libcomerr2 1.41.11-1 common error description library
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libgssapi-krb5-2 1.8.1+dfsg-2 MIT Kerberos runtime libraries - k
ii libgssglue1 0.1-4 mechanism-switch gssapi library
ii libk5crypto3 1.8.1+dfsg-2 MIT Kerberos runtime libraries - C
ii libkrb5-3 1.8.1+dfsg-2 MIT Kerberos runtime libraries
ii libnfsidmap2 0.23-2 An nfs idmapping library
ii librpcsecgss3 0.19-2 allows secure rpc communication us
ii libwrap0 7.6.q-18 Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii netbase 4.41 Basic TCP/IP networking system
ii portmap 6.0.0-2 RPC port mapper
ii ucf 3.0025 Update Configuration File: preserv
nfs-common recommends no packages.
nfs-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:1.2.2-3
We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive:
nfs-common_1.2.2-3_i386.deb
to main/n/nfs-utils/nfs-common_1.2.2-3_i386.deb
nfs-kernel-server_1.2.2-3_i386.deb
to main/n/nfs-utils/nfs-kernel-server_1.2.2-3_i386.deb
nfs-utils_1.2.2-3.debian.tar.bz2
to main/n/nfs-utils/nfs-utils_1.2.2-3.debian.tar.bz2
nfs-utils_1.2.2-3.dsc
to main/n/nfs-utils/nfs-utils_1.2.2-3.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 582...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings <b...@decadent.org.uk> (supplier of updated nfs-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 08 Aug 2010 23:43:42 +0100
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: i386 source
Version: 1:1.2.2-3
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: Ben Hutchings <b...@decadent.org.uk>
Closes: 579397 582003
Description:
nfs-common - NFS support files common to client and server
nfs-kernel-server - support for NFS kernel server
Changes:
nfs-utils (1:1.2.2-3) unstable; urgency=low
.
* mount.nfs: Preserve explicit port=2049 option (Closes: #582003)
* rpc.statd: Allow monitoring of addresses without names (Closes: #579397)
* Add control fields pointing to the new git repository
Checksums-Sha1:
09070f7f828b3084df6388ce4d38f1431875a62f 2076 nfs-utils_1.2.2-3.dsc
bfa845e60c615f8d47d1d1734b905434d4060abc 33694 nfs-utils_1.2.2-3.debian.tar.bz2
76d3a082ff66cdcc2d1944a79eb208153726e1c5 158822
nfs-kernel-server_1.2.2-3_i386.deb
9353c6d21702b476039c7bacb439c91cd93fc4c3 226390 nfs-common_1.2.2-3_i386.deb
Checksums-Sha256:
40d4a95efb3414279d3fad709bb345e39c2cee1eaa0910cd1d29ebf64427c1ab 2076
nfs-utils_1.2.2-3.dsc
41eb9779ffcbbee348f04c2abb245f19778abf49b7621fbec296e1e3781f3b3c 33694
nfs-utils_1.2.2-3.debian.tar.bz2
cb92bd2e8f4e7d686b952b1c84b64580f2f75977ff56c48dba67f44c0b2bc117 158822
nfs-kernel-server_1.2.2-3_i386.deb
935b6457b69f7bc91ab2bfdb57a49cb3388f1c09ada5be3c07c1f009b9651784 226390
nfs-common_1.2.2-3_i386.deb
Files:
11ad110a57b6e36ea601fbe15f26f268 2076 net standard nfs-utils_1.2.2-3.dsc
de117d46ebbdea509cd0c87d2d2efdf6 33694 net standard
nfs-utils_1.2.2-3.debian.tar.bz2
660914dcbabb4fe17a773b84df0bca6d 158822 net optional
nfs-kernel-server_1.2.2-3_i386.deb
c2908bcdd9082ce54ee57515390bdac7 226390 net standard
nfs-common_1.2.2-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIVAwUBTF81b+e/yOyVhhEJAQo97A//cebD5QvFoew0DRbS4O4g+EntQe/COi/m
snWIvDglkqTiBrl0gng42H5ck02cQQHNFRt2eayjAwC/wKLIavA09OgfaQ5OLEkq
niJYGLx7E4/JGRLa1/yFSZvy+h8BOw9MtjXPhXnWBNPBNZ5H1uJ4diVvWY3CrhrF
e3LsJGvLOb+mP2LGlr+hzgbRJSJFy9syP18WQqkyliUPUm5okNSFgQ1fk8V5RhjW
Am2Ra9kvVejyA/HThjTf8qGm/fcRaYA7tgSSJC6xJzI4Hvlm4TkMqZatA1eVjfSm
17ax+axgvs5mx11QymkqZQbVv1wh0t8wx1+KgKwogXvuvjzkA8v/cl+vZ6vP1BZc
rzH/EAiN78Xa9KRXEqhcn74b5fG4x3HQ3+bbCCZXKgQ75c8vlkSPe+m8drOeXHvc
K/8WMI+SVhsC8KoM7vd1exlKv4CLYB8Ftilwuueulv0AvfwZhQvhQ/+/Qs59opk2
lDQigutkxLttVUJAW2BXbMTC2TWPyOE9Qgx8QrgYWQS7VE6vH7mIvqaxQ/QGm4As
wvtAPvyi0TcMTq3kotnGNdEwuWsWTyjZjOJgxNTuguB6i7wwjAm/HSIO4WrCsLJk
KqUAAQYo67FvqFwJMOYpVUxnFW+QDSBASJi3HSY59OpJJSOIBNcj5LEPBobL7zVD
yoRpR0NSH5g=
=WD/J
-----END PGP SIGNATURE-----
--- End Message ---
