From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jaco Kroon <jkroon@cs.up.ac.za>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NFS lockups+empty directories
Date: Thu, 24 Jun 2004 16:01:11 -0400 [thread overview]
Message-ID: <1088107270.5194.24.camel@lade.trondhjem.org> (raw)
In-Reply-To: <40DAA4AA.5000102@cs.up.ac.za>
På to , 24/06/2004 klokka 05:53, skreiv Jaco Kroon:
> Hello there
>
> I'm having 2 problems with nfs atm, I'll first describe the problem of
> the mysterious deadlocks.
>
> On the client that has deadlocked I see these (tcpdump host servername -n)
> 11:37:31.272353 IP 137.215.40.16.3750658894 > 137.215.98.25.2049: 140
> read [|nfs]
> 11:37:32.671933 IP 137.215.40.16.3717104462 > 137.215.98.25.2049: 140
> read [|nfs]
> 11:37:33.371732 IP 137.215.40.16.3733881678 > 137.215.98.25.2049: 140
> read [|nfs]
>
> On the server I get lots and lots of these (tcpdump host clientname -n)
> 11:39:23.239369 IP 137.215.40.16.3733881678 > 137.215.98.25.2049: 140
> read [|nfs]
> 11:37:03.280950 IP 137.215.98.25.2049 > 137.215.40.16.3717104462: reply
> ok 1472 read [|nfs]
> 11:37:03.280965 IP 137.215.98.25 > 137.215.40.16: udp
> 11:37:03.280975 IP 137.215.98.25 > 137.215.40.16: udp
> 11:37:03.280986 IP 137.215.98.25 > 137.215.40.16: udp
> 11:37:03.280997 IP 137.215.98.25 > 137.215.40.16: udp
> 11:37:03.281008 IP 137.215.98.25 > 137.215.40.16: udp
>
> The port numbers are *obviously* wrong, but I suspect this is a tcpdump
> problem. What worries me is that it doesn't look like the packets from
> the server reaches the client.
You are using UDP: There are never any guarantees there that the packets
from the server will actually reach the client. Now please read the
sections in the NFS FAQ and HOWTOs about this sort of problem:
http://nfs.sourceforge.net/
Cheers,
Trond
prev parent reply other threads:[~2004-06-24 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 9:53 Jaco Kroon
2004-06-24 20:01 ` Trond Myklebust [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=1088107270.5194.24.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=jkroon@cs.up.ac.za \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®