From: Timothy Miller <theosib@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HELP: NFS mount hangs when attempting to copy file
Date: Sat, 23 Jul 2005 22:52:21 -0400 [thread overview]
Message-ID: <9871ee5f05072319523528f2de@mail.gmail.com> (raw)
In-Reply-To: <1122135532.8203.5.camel@lade.trondhjem.org>
On 7/23/05, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> I beg to disagree. A lot of these VPN solutions are unfriendly to MTU
> path discovery over UDP. Sun uses TCP by default when mounting NFS
> partitions. Have you tried this on your Linux box?
I changed the protocol to TCP and changed rsize and wsize to 1024. I
don't know which of those fixed it, but I'm going to leave it for now.
As for MTU, yeah, the Watchguard box seems to have some hard-coded
limits, and for whatever reason KDE and GNOME graphical logins do
something that exceeds those limits, completely independent of NFS,
and hang up hard.
Thanks.
next prev parent reply other threads:[~2005-07-24 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 22:56 HELP: NFS mount hangs when attempting to copy file Timothy Miller
2005-07-23 16:18 ` Trond Myklebust
2005-07-24 2:52 ` Timothy Miller [this message]
2005-07-24 11:38 ` Michael Clark
2005-07-25 14:34 ` Roger Heflin
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=9871ee5f05072319523528f2de@mail.gmail.com \
--to=theosib@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox