From: bert hubert <ahu@ds9a.nl>
To: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: nfs/nfsd gets stuck on a write
Date: Wed, 6 Aug 2003 13:02:16 +0200 [thread overview]
Message-ID: <20030806110215.GA30936@outpost.ds9a.nl> (raw)
In-Reply-To: <20030806104612.GB703@wiggy.net>
On Wed, Aug 06, 2003 at 12:46:13PM +0200, Wichert Akkerman wrote:
> I seem to have hit a nfs problem between two 2.6.0-test2 machines.
> Mounting works properly, but at some point when logging in with /home
> over NFS things get stuck. A tcpdump reveals the following:
I've had problems like that go away by explicitly mounting -o tcp.
> Both machines have a similar configuration: 2.6.0-test2 with NFS and NFS
> over TCP enabled. There are no firewalls blocking traffic between those
> two machines.
Your dump shows UDP, so give it a try.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2003-08-06 11:02 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 [this message]
2003-08-06 11:16 ` Wichert Akkerman
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=20030806110215.GA30936@outpost.ds9a.nl \
--to=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