linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Ray Van Dolson <rvandolson-v48TKWNzwFw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Proper way to request async from NFS server?
Date: Tue, 05 Jan 2010 10:39:22 -0500	[thread overview]
Message-ID: <4B435D2A.7040009@redhat.com> (raw)
In-Reply-To: <20100105075610.GA435-v48TKWNzwFw@public.gmane.org>

Ray Van Dolson wrote:
> 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.
> 

Simply mounting with no specific options should cause the
client to generate WRITE requests with the appropriate setting.
When it can, the client generates UNSTABLE requests followed
by COMMIT operations.  When it is required to, the client
generates FSYNC requests.

If you are only seeing FSYNC requests over the wire, then I
might suggest checking the application to see how it opens
the file.

		ps

      parent reply	other threads:[~2010-01-05 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05  7:56 Proper way to request async from NFS server? Ray Van Dolson
     [not found] ` <20100105075610.GA435-v48TKWNzwFw@public.gmane.org>
2010-01-05 15:39   ` Peter Staubach [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=4B435D2A.7040009@redhat.com \
    --to=staubach@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rvandolson-v48TKWNzwFw@public.gmane.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).