An NFS server supports only NFS version <4.
This server is unreachable at a certain time.
A Debian client boots and tries to mount a directory on the server with
the 'bg' option, but without the 'nfsvers' option.
Later, the NFS server comes up.
Result: The client does _not_ mount the directory and the background
mount is silently terminated. This typically breaks cross-mounted
server scenarios.
[Note that specifying 'nfsvers=3' is NOT a workaround, because then
failing to connect the portmapper already terminates the mount.nfs
process and no backgrounding happens at all. This is a separate
bug IMHO.]
Analysis: When first trying an NFSv4 mount, 'vers=4' is appended
to the extra_options string in the mount options. Then, the next
(background) attempt also happens with vers=4 and consequently,
nfs_try_mount_v3v2() is never called. The mount fails, even though
the V3 server would now be reachable.
Fix appended. It looks like this bug is also present in current
Debian nfs-utils git.
+ /*
+ * If success, update option string to be recorded in /etc/mtab.
+ */
+ if (result) {
+ free(*mi->extra_opts);
+ *mi->extra_opts = extra_opts;
+ } else
+ free(extra_opts);
+
out_fail:
po_destroy(options);
return result;
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: u4bogahv55.fsf@mail.malloc.de">http://lists.debian.org/u4bogahv55.fsf@mail.malloc.de