mount.nfs: chk_mountpoint()

[Chuck Lever <chuck.lever@oracle.com>]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Hi all-

The recent addition of the chk_mountpoint() function in 
utils/mount/mount.c in nfs-utils commit 3b55934b has broken a particular 
behavior of background mounts.

nfs(5) states that, if the "bg" option is specified, "A missing mount 
point is treated as a timeout, to allow for nested NFS mounts."

If I try mounting an NFS share onto a non-existent directory while using 
the "bg" option, I now get an immediate failure:

   mount.nfs: mount point /mnt/nothere does not exist

instead of the mount backgrounding itself to wait for /mnt/nothere to 
show up.  This is because chk_mountpoint() is causing the mount request 
to fail immediately.

Is the documented bg retry behavior still desirable?

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs