From: Lee Revell <rlrevell@joe-job.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Justin Piszcz" <jpiszcz@lucidpixels.com>,
"Trond Myklebust" <trond.myklebust@fys.uio.no>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Tomasz Kłoczko" <kloczek@rudy.mif.pg.gda.pl>,
"Phil Oester" <kernel@linuxace.com>,
linux-kernel@vger.kernel.org, apiszcz@lucidpixels.com
Subject: Re: Kernel 2.6.15.1 + NFS is 4 times slower than FTP!?
Date: Tue, 17 Jan 2006 17:13:53 -0500 [thread overview]
Message-ID: <1137536034.19678.43.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0601172307030.7756@yvahk01.tjqt.qr>
On Tue, 2006-01-17 at 23:07 +0100, Jan Engelhardt wrote:
> > auto Can be mounted with the -a option.
> >
> > defaults
> > Use default options: rw, suid, dev, exec, auto,
> > nouser, and async.
> >
> > The default is async, no?
>
> The server side also needs to specify async in exports. You even get a
> warning if you do not specify sync or async, because the default had
> been changed once.
>
What is the date on the above man page? Looks like the docs need to be
updated.
I believe the default was originally async, which violates the NFS spec
and is dangerous, and changed to sync at some point.
Lee
next prev parent reply other threads:[~2006-01-17 22:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 1:07 Kernel 2.6.15.1 + NFS is 4 times slower than FTP!? Justin Piszcz
2006-01-17 1:23 ` Phil Oester
2006-01-17 1:32 ` Justin Piszcz
2006-01-17 17:48 ` Tomasz Kłoczko
2006-01-17 18:11 ` Alan Cox
2006-01-17 18:24 ` Justin Piszcz
2006-01-17 18:33 ` Alan Cox
2006-01-17 18:37 ` Trond Myklebust
2006-01-17 18:38 ` Justin Piszcz
2006-01-17 18:53 ` Trond Myklebust
2006-01-17 18:55 ` Justin Piszcz
2006-01-17 19:01 ` Trond Myklebust
2006-01-17 19:03 ` Justin Piszcz
2006-01-17 20:39 ` Jan Engelhardt
2006-01-17 20:45 ` Justin Piszcz
2006-01-17 22:07 ` Jan Engelhardt
2006-01-17 22:13 ` Lee Revell [this message]
2006-01-17 23:19 ` Justin Piszcz
2006-01-17 23:39 ` Lee Revell
2006-01-18 0:43 ` Trond Myklebust
2006-01-17 9:50 ` Justin Piszcz
2006-01-17 17:10 ` Jan Engelhardt
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=1137536034.19678.43.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apiszcz@lucidpixels.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jpiszcz@lucidpixels.com \
--cc=kernel@linuxace.com \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.