On Thu, Nov 26, 2009 at 16:20, Trond Myklebust
<trond.myklebust@xxxxxxxxxx> wrote:
>> I can run with RPCDBG_TRANS enabled, if it is needed to further
>> pinpoint the problem.
I don't think I understand how to enable RPCDBG_TRANS exactly.
Anyway, I activated the dprintks in xprtsock.c with the following
(endless) result:
RPC: cfa94400 connect status 99 connected 0 sock state 7
RPC: xs_tcp_send_request(32896) = -32
RPC: xs_tcp_state_change client cfa94400...
RPC: state 7 conn 0 dead 0 zapped 1
RPC: xs_connect delayed xprt cfa94400 for 0 seconds
RPC: worker connecting xprt cfa94400 to address: addr=1.2.3.151
port=2049 proto=tcp
RPC: cfa94400 connect status 99 connected 0 sock state 7
RPC: xs_tcp_send_request(32896) = -32
RPC: xs_tcp_state_change client cfa94400...
RPC: state 7 conn 0 dead 0 zapped 1
RPC: xs_connect delayed xprt cfa94400 for 0 seconds
RPC: worker connecting xprt cfa94400 to address: addr=1.2.3.151
port=2049 proto=tcp
RPC: cfa94400 connect status 99 connected 0 sock state 7
RPC: xs_tcp_send_request(32896) = -32
RPC: xs_tcp_state_change client cfa94400...
RPC: state 7 conn 0 dead 0 zapped 1
RPC: xs_connect delayed xprt cfa94400 for 0 seconds
RPC: worker connecting xprt cfa94400 to address: addr=1.2.3.151
port=2049 proto=tcp
Does this tell you more?
--
Sincerely,
Stephen R. van den Berg.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
