Re: 2.4.19+trond and diskless locking problems

Trond Myklebust (trond.myklebust@fys.uio.no)
Wed, 27 Nov 2002 02:14:50 +0100


>>>>> " " == Christian Reis <kiko@async.com.br> writes:

> a) ps ax | grep lockd returns:

> 94 ? DW 0:00 [lockd]

> Why would lockd be in state "D"? Looks bad. Can this happen
> in normal usage? It kicks the loadavg up 1 point.
<snip>
> [ 10-second delay here ]

> 09:24:18.988289 violinux.async.com.br.793 >
> anthem.async.com.br.sometimes-rpc4: udp 180 (DF)

> [ 11-second delay here ]

OK, so you are sending out the RPC request to the server's NLM daemon,
which is clearly receiving the packet (since tcpdump was able to log
it), but is never sending a reply. Are you seeing any kernel messages
in the syslog?

BTW: the tcpdumps you're showing are all UDP, not TCP...

Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/