Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Dick Streefland <dick.streefland@altium.nl>
Cc: nfs@lists.sourceforge.net
Subject: Re: inconsistencies in nfs(5)
Date: Thu, 09 Aug 2007 12:27:07 -0400	[thread overview]
Message-ID: <46BB405B.5050206@oracle.com> (raw)
In-Reply-To: <169a.46bb3b18.7157f@altium.nl>

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

rnews@tasking.nl wrote:
> Chuck Lever <chuck.lever@oracle.com> wrote:
> | +  The description for the "bg" option claims "After a mount operation 
> | is backgrounded, all subsequent mounts on the same NFS server will be 
> | backgrounded immediately, without first attempting the mount."  I don't 
> | think there's logic to do that in either the legacy mount command or in 
> | mount.nfs.  Should this text be removed from the man page?
> 
> I added that text in 1997, in a patch that was included in mount-2.7g.
> It referred to the following fragment in nfsmount.c:
> 
> +       /*
> +        * If the previous mount operation on the same host was
> +        * backgrounded, and the "bg" for this mount is also set,
> +        * give up immediately, to avoid the initial timeout.
> +        */
> +       if (bg && !running_bg &&
> +           prev_bg_host && strcmp(hostname, prev_bg_host) == 0) {
> +               if (retry > 0)
> +                       retval = EX_BG;
> +               return retval;
> +       }
> 
> This code got removed somewhere after util-linux-2.12p, but I don't
> know the details.

This is still in utils/mount/nfsmount.c.

I'm not sure how this can affect other mount commands running 
concurrently on the same client.  The man page implies that if one mount 
command has backgrounded against a server, subsequent mount commands 
against the same server will just go right into the background.  But 
prev_bg_host is unique in each instance of the mount command.

Can you help me understand what you intended?  Do you have a test case?

[-- 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-09 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 15:08 inconsistencies in nfs(5) Chuck Lever
2007-08-09 16:04 ` rnews
2007-08-09 16:27   ` Chuck Lever [this message]
2007-08-10  8:18     ` rnews
2007-08-13 14:18       ` Chuck Lever
2007-08-15 20:34       ` Chuck Lever

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=46BB405B.5050206@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=dick.streefland@altium.nl \
    --cc=nfs@lists.sourceforge.net \
    /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