From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christian Robottom Reis <kiko@async.com.br>
Cc: <NFS@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>,
<reiserfs-list@namesys.com>
Subject: Re: [NFS] NFS insanity
Date: 22 Jun 2001 14:58:53 +0200 [thread overview]
Message-ID: <shsvgloisc2.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.32.0106211942580.322-100000@blackjesus.async.com.br>
In-Reply-To: Christian Robottom Reis's message of "Thu, 21 Jun 2001 19:43:28 -0300 (BRT)"
>>>>> " " == Christian Robottom Reis <kiko@async.com.br> writes:
> anthem:/mondo /mondo nfs
> defaults,rsize=3072,wsize=3072,suid,async 0 0
> Async is on, but it's there by default IIRC, right?
Nope. The 'async' option is meaningless to the NFS client. Should make
no difference though, as it's never checked.
I'm a bit surprised about your choice or rsize and wsize. Although it
shouldn't make any difference, 3072 is not a natural size on an x86
machine. You usually want something that divides PAGE_CACHE_SIZE=4096.
Furthermore, on the Linux NFS client, any value < PAGE_CACHE_SIZE
means that you use synchronous writes (deferred writes are enabled
with wsize=4096 or greater).
The advantage in this case though, is that it means any error message
that was returned by the server was guaranteed to have been received
by 'cp', because the page was written to the server immediately.
If I were you therefore, I'd use ethereal or tcpdump to sniff the NFS
traffic and check that the file indeed gets reproduced correctly on
the wire.
Cheers,
Trond
next prev parent reply other threads:[~2001-06-22 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 23:23 NFS insanity Christian Robottom Reis
2001-06-21 13:59 ` [reiserfs-list] " Chris Mason
2001-06-21 14:58 ` Trond Myklebust
2001-06-21 15:10 ` [NFS] " Trond Myklebust
2001-06-21 22:43 ` Christian Robottom Reis
2001-06-22 12:58 ` Trond Myklebust [this message]
2001-06-22 15:57 ` Christian Robottom Reis
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=shsvgloisc2.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox