All of lore.kernel.org
 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: Wed, 15 Aug 2007 16:34:11 -0400	[thread overview]
Message-ID: <46C36343.8000009@oracle.com> (raw)
In-Reply-To: <5e6a.46bc1f6e.593b@altium.nl>

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

rnews@tasking.nl wrote:
> Chuck Lever <chuck.lever@oracle.com> wrote:
> | This is still in utils/mount/nfsmount.c.
> 
> It is not in util-linux-ng-2.13-rc2 anymore, which is in Debian sid.
> 
> | 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?
> 
> Phew, I wrote that 10 years ago! But I think that when you do a
> "mount -atnfs", multiple mounts will be handled by the same mount
> instance. The code helps when there are multiple NFS mounts from the
> same host in fstab, and the server is down when you boot the client.

OK, looking at this again...

I haven't actually tested this, but I think that "mount -a" will invoke 
the mount.nfs helper repeatedly for each individual NFS mount request. 
I don't see any support for a "-a" option in mount.nfs; it seems to be 
designed specifically for handling individual NFS mount requests, and 
not for "mount all items in /etc/fstab with this fstype."

Thus I don't think this feature you describe can work any more, and it 
argues perhaps for shortening the bg timeout in mount.nfs.  Comments?

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

      parent reply	other threads:[~2007-08-15 20:36 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
2007-08-10  8:18     ` rnews
2007-08-13 14:18       ` Chuck Lever
2007-08-15 20:34       ` Chuck Lever [this message]

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=46C36343.8000009@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.