Re: NFS lockups+empty directories

[Trond Myklebust]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/