From: Wichert Akkerman <wichert@wiggy.net>
To: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Cc: bert hubert <ahu@ds9a.nl>
Subject: Re: nfs/nfsd gets stuck on a write
Date: Wed, 6 Aug 2003 13:16:34 +0200 [thread overview]
Message-ID: <20030806111634.GG703@wiggy.net> (raw)
In-Reply-To: <20030806110215.GA30936@outpost.ds9a.nl>
Previously bert hubert wrote:
> I've had problems like that go away by explicitly mounting -o tcp.
Mounting with -o tcp does indeed seem to be a working work-around. It
does feel a lot more sluggish/high latency than udp though.
Wichert.
--
Wichert Akkerman <wichert@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
prev parent reply other threads:[~2003-08-06 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 10:46 nfs/nfsd gets stuck on a write Wichert Akkerman
2003-08-06 11:02 ` bert hubert
2003-08-06 11:16 ` Wichert Akkerman [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=20030806111634.GG703@wiggy.net \
--to=wichert@wiggy.net \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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).