From: Ray Van Dolson <rvandolson-v48TKWNzwFw@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Proper way to request async from NFS server?
Date: Mon, 4 Jan 2010 23:56:10 -0800 [thread overview]
Message-ID: <20100105075610.GA435@esri.com> (raw)
RHEL 5.4 NFSv3 client accessing a Solaris 10 NFS export.
Solaris 10 does not offer a way to specify whether a given share is
async or sync as the Linux NFS server does. As far as I understand it,
its NFS server will honor whatever the connecting NFS client requests.
I'm mounting a Solaris NFS share with -o async (or using async in the
options field in fstab). Though this completes without complaint, I
don't see "async" listed in the mount options under /proc/mounts and
when I do a snoop on the Solaris side, all the write requests are FSYNC
instead of ASYNC.
Am I doing something wrong? What's the correct way to get the Linux
NFS client to request asynchronous operation?
This is with nfs-utils 1.0.9 and of course, the RHEL5 kernel
2.6.18-164.6.1.el5.
Thanks,
Ray
next reply other threads:[~2010-01-05 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 7:56 Ray Van Dolson [this message]
[not found] ` <20100105075610.GA435-v48TKWNzwFw@public.gmane.org>
2010-01-05 15:39 ` Proper way to request async from NFS server? Peter Staubach
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=20100105075610.GA435@esri.com \
--to=rvandolson-v48tkwnzwfw@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).