[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#560388: marked as done (mount.nfs4: 'bg' option is not implemented; 'fg' doesn't work as expected)

Your message dated Sun, 27 Mar 2011 17:32:11 +0000
with message-id <E1Q3tox-0001at-VS@franck.debian.org>
and subject line Bug#560388: fixed in nfs-utils 1:1.2.3-1
has caused the Debian Bug report #560388,
regarding mount.nfs4: 'bg' option is not implemented; 'fg' doesn't work as expected
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 owner@bugs.debian.org
immediately.)


-- 
560388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560388
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 

Package: nfs-common
Version: 1:1.1.2-6lenny1
Severity: important


Unfortunately the nfs(5) man page and the actual source code don't
agree regarding the use of the 'bg' mount option. The man page specifies
that after a failed attempt of mounting the export, the mount process
forks into the background and tries again for 'retry' minutes. What really
happens in this case is the same as if 'fg' was specified, so any other
error than a timeout will cause the mount to fail and never try again.
This is rather unfortunate, as I have a system where I get 'network
unreachable' errors for a few seconds after the eth0 interface is brought
up; this normally shouldn't cause any trouble, as I'm using the 'bg' flag,
but with this bug, the mount just never completes.

What would be even better is to fix the 'fg' mount as well (and this
applies also to version 2/3 of mount.nfs), so that it doesn't treat all
errors as permanent failures; as this example shows, some unreachables
could indicate temporary conditions. In fact, the best approach would be
to try again for 'retry' minues regardless the cause of failure. That way
the mount in my case would work even without 'bg' and it would also be
possible for example to wait for an nfs server to come up during boot.
Consider the scenario where both the nfs client and the server boot up at
the same time, but it takes a few more seconds for the server to start the
nfs daemon than for the client to start the mount: the client gets a
"connection refused" error and immediately* boots up without the mount,
unless special care has been taken to prevent that.
*: Not quite correct, as there's a script that waits for the network
mounts to complete before starting other initscripts. It's pointless here
but will delay the boot process for a few minutes.

I just checked, and on systems where the NFS implementation is more
mature (Solaris, for example), the behaviour is the same as I described
above: an 'fg' mount will block and wait until it times out, no matter
what is the cause of the delay.


How to reproduce:


# mount.nfs4 ip-that-times-out:/ /mnt -o bg
<sits here for some time, definitely more than 2 minutes, probably 10000>

syslog:
mount[7347]: mount to NFS server 'ip-that-times-out' failed: timed out, retrying
(once every 20 seconds)




# mount.nfs4 connrefused:/ /mnt -o bg
#

syslog:
mount[3742]: mount to NFS server 'connrefused' failed: System Error: Connection refused, giving up




# time mount.nfs4 connrefused:/ /mnt
mount.nfs4: mount to NFS server 'connrefused' failed: System Error: Connection refused

real    0m0.002s
user    0m0.000s
sys     0m0.000s
#



And there's one more, related to the same paragraph of the man page:

# mount x:/ /nonexistent -o bg
mount.nfs: mount point /nonexistent does not exist
#

"If the local mount point directory is missing, the mount(8) command acts as if the mount request timed out."
Apparently it doesn't. Not even for v3.




Best regards,

Matyas Koszik

--- End Message ---
--- Begin Message --- 
Source: nfs-utils
Source-Version: 1:1.2.3-1

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.3-1_i386.deb
  to main/n/nfs-utils/nfs-common_1.2.3-1_i386.deb
nfs-kernel-server_1.2.3-1_i386.deb
  to main/n/nfs-utils/nfs-kernel-server_1.2.3-1_i386.deb
nfs-utils_1.2.3-1.debian.tar.bz2
  to main/n/nfs-utils/nfs-utils_1.2.3-1.debian.tar.bz2
nfs-utils_1.2.3-1.dsc
  to main/n/nfs-utils/nfs-utils_1.2.3-1.dsc
nfs-utils_1.2.3.orig.tar.bz2
  to main/n/nfs-utils/nfs-utils_1.2.3.orig.tar.bz2



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 560388@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes <luk@debian.org> (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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 27 Mar 2011 18:54:45 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source i386
Version: 1:1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: Luk Claes <luk@debian.org>
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 441361 474037 528939 560388 585085 610363 612933
Changes: 
 nfs-utils (1:1.2.3-1) unstable; urgency=low
 .
   * New upstream release
     - 7-remove-duplicate-exports-paragraphs : removed
     - 12-svcgssd-document-n-option: updated
     - 14-allow-address-without-name : removed
     - 15-mountd-fix-path-comparison-for-v4-crossmnt : removed
     - 16-mount.nfs.man-nfs.man-update-distinction-between-fstypes:
       part about nfs.man removed and
       renamed to 16-mount.nfs.man-update-distinction-between-fstypes
     - mountd: fix --manage-gids hang due to int/uint bug (0f05c8a)
       (Closes: #528939,585085)
     - mount.nfs: Don't do anything fancy if this is a remount (f11547f)
       (Closes: #612933)
     - mount: Mount should retry unreachable hosts (5a355f4)
       (Closes: #560388)
     - Try to use kernel function to determine supported Kerberos
       enctypes (258f10f) (Closes: #474037)
     - nfs-common: Add Recommends python for mountstats and nfsiostat
   * Make sure everything is shipped (inspired by #594933)
   * nfs-common.init: Enable idmapd by default (Closes: #610363)
   * Install bug scripts to ease debuging
   * Build depend on libtirpc-dev and enable IPv6 (Closes: #441361)
Checksums-Sha1: 
 73c798e75ea2383ff52b35d1f4a126eff4f75096 1486 nfs-utils_1.2.3-1.dsc
 da70a29191b07056d71b6e427a87d5cfd8628523 672759 nfs-utils_1.2.3.orig.tar.bz2
 6250529f8d059b1a8ac41c6af07994869108bb74 34766 nfs-utils_1.2.3-1.debian.tar.bz2
 6f28acf65cd986b44f2b2d8636317cc3053b943b 153014 nfs-kernel-server_1.2.3-1_i386.deb
 56b5a8ab3eca6f10c779c4708a787e4b2fadac78 238680 nfs-common_1.2.3-1_i386.deb
Checksums-Sha256: 
 9f073630b852082d8a8a9fcc44d9862453b25f21837ffd9d88c207bc8cf4049f 1486 nfs-utils_1.2.3-1.dsc
 5575ece941097cbfa67fbe0d220dfa11b73f5e6d991e7939c9339bd72259ff19 672759 nfs-utils_1.2.3.orig.tar.bz2
 3e5d5fa173ecf8597d996565ca6a2932a7b0a4ea9ef3197e46bbb3d527a3ccdd 34766 nfs-utils_1.2.3-1.debian.tar.bz2
 5126b4374a789d9ad3f9d817eb1e558931914edfe177660cf981d760d04d016d 153014 nfs-kernel-server_1.2.3-1_i386.deb
 07b68d201ef9d8668a839d8c533bef4205d04f6215c84a45f1f102cba060cd76 238680 nfs-common_1.2.3-1_i386.deb
Files: 
 72abcfe642257f0579d14c54590ae8f8 1486 net standard nfs-utils_1.2.3-1.dsc
 1131dc5f27c4f3905a6e7ee0d594fd4d 672759 net standard nfs-utils_1.2.3.orig.tar.bz2
 d9de93233d39669b2207ea9694911630 34766 net standard nfs-utils_1.2.3-1.debian.tar.bz2
 aa9e1a2f770d8a9855793535d89f59c3 153014 net optional nfs-kernel-server_1.2.3-1_i386.deb
 81790c7ffec2ccc3ad713d23802f1d96 238680 net standard nfs-common_1.2.3-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk2PcJMACgkQ5UTeB5t8Mo3DxACePOeosewmAxKKFFn3zNz27xMe
nS8AnRfvi7XjUIgmeJxvc7WAKvK7Q6Fp
=fo5P
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: