From: Chuck Lever <chuck.lever@oracle.com>
To: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: inconsistencies in nfs(5)
Date: Thu, 09 Aug 2007 11:08:34 -0400 [thread overview]
Message-ID: <46BB2DF2.1050501@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Trying to get a handle on how individual mount options behave, I'm
rewriting nfs(5). Jeff Layton pointed out a few inconsistencies and
I've found a few more. I'd like to resolve these:
+ The default "intr" behavior for nfs and nfs4 is not the same.
According to the code, for nfs the default is "nointr" and for nfs4 the
default is "intr". Is this the desired behavior?
+ "nocto" and "noac" are listed as valid nfs4 mount options. I believe
"nocto" can't be supported by the NFSv4 protocol because an OPEN on the
wire is always necessary. Is "noac" supported for nfs4 file systems?
+ Is the "noacl" option still supported in 2.6.latest? What exactly
does it do, and what are the consequences of using it?
+ 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?
Likely more to come...
[-- 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
next reply other threads:[~2007-08-09 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 15:08 Chuck Lever [this message]
2007-08-09 16:04 ` inconsistencies in nfs(5) 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
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=46BB2DF2.1050501@oracle.com \
--to=chuck.lever@oracle.com \
--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.