From: "J. Bruce Fields" <bfields@fieldses.org>
To: lyndat3@your-mail.com
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: file xfer over NFSv4 with 'sync' ~300X slower than with 'async' ?
Date: Wed, 1 Apr 2015 15:56:03 -0400 [thread overview]
Message-ID: <20150401195603.GG3040@fieldses.org> (raw)
In-Reply-To: <1427915047.1810469.248215805.54189CB6@webmail.messagingengine.com>
On Wed, Apr 01, 2015 at 12:04:07PM -0700, lyndat3@your-mail.com wrote:
> Hi
>
> > > Yes. This is a common source of confusion. In retrospect maybe the
> > > export sync/async option should have had a different name from the
> > > client mount option.--b.
> > >
> >
> > Do we still need a server 'async' export option? Who is still using
> > NFSv2 for any type of performance-critical work?
>
>
> Just to be clear -- MY pebkac was that I'd set the CLIENT mount as 'sync' -- based on the misunderstanding that write integrity required it 'everywhere' -- on the export AND the mount -- and that 'async' was potentially unsafe.
>
> The server was always exporting 'sync'.
Yeah, understood, I just meant that if we'd originally named that export
option, I don't know, "trash_me_on_reboot", then you wouldn't have
gotten the "don't use async, it's unsafe" idea, and wouldn't have gotten
into this mess. But, too late to do anything about that, I guess.
--b.
next prev parent reply other threads:[~2015-04-01 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 21:44 large data transfer rate slowdows over NFSv4 local lan with kernel 3.19x & 3.16x ? lyndat3
2015-03-31 14:21 ` file xfer over NFSv4 with 'sync' ~300X slower than with 'async' ? lyndat3
2015-04-01 17:54 ` J. Bruce Fields
2015-04-01 18:02 ` lyndat3
2015-04-01 18:51 ` J. Bruce Fields
2015-04-01 18:59 ` Trond Myklebust
2015-04-01 19:04 ` lyndat3
2015-04-01 19:56 ` J. Bruce Fields [this message]
2015-04-01 20:02 ` Trond Myklebust
2015-04-01 20:24 ` lyndat3
2015-04-01 19:50 ` J. Bruce Fields
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=20150401195603.GG3040@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lyndat3@your-mail.com \
--cc=trond.myklebust@primarydata.com \
/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.