Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Peter Staubach <staubach@redhat.com>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: mount.nfs: chk_mountpoint()
Date: Thu, 23 Aug 2007 13:45:52 -0400	[thread overview]
Message-ID: <46CDC7D0.6030803@oracle.com> (raw)
In-Reply-To: <46CD82A0.1000408@redhat.com>

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

Peter Staubach wrote:
> Chuck Lever wrote:
>> 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? 
> 
> Isn't this what autofs is for?  To be able to handle hierarchies
> of mounts?

I think the purpose of this feature is to allow a sysadmin to specify a 
set of mount points in /etc/fstab, some possibly nested.  "mount -a 
-tnfs" should work no matter what order the mounts in /etc/fstab are 
specified.

After all, some servers may be unresponsive when the client boots -- the 
mounting order is nondeterministic; it can't be depended on, in any event.

We also don't know if the automounter itself depends on this feature.

[-- 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

  reply	other threads:[~2007-08-23 18:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 19:02 mount.nfs: chk_mountpoint() Chuck Lever
2007-08-23 12:50 ` Peter Staubach
2007-08-23 17:45   ` Chuck Lever [this message]
2007-08-23 18:22     ` Peter Staubach
2007-08-23 20:00       ` Chuck Lever
2007-08-23 20:12         ` Peter Staubach
2007-08-23 20:30           ` Chuck Lever
2007-08-23 20:49             ` Peter Staubach
2007-08-30 10:12           ` Frank van Maarseveen
2007-08-30 11:53             ` Peter Staubach
2007-08-30 16:01               ` Chuck Lever
2007-08-30 16:07                 ` Peter Staubach
2007-08-30 16:18                   ` Chuck Lever
2007-08-30 19:15                     ` Talpey, Thomas
2007-08-30 21:11                       ` Peter Staubach
2007-08-30 16:19                   ` J. Bruce Fields
2007-08-30 16:24                     ` Chuck Lever
2007-08-30 16:16               ` Frank van Maarseveen

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=46CDC7D0.6030803@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=staubach@redhat.com \
    /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