From: Olaf Kirch <okir@suse.de>
To: nfs@lists.sourceforge.net
Subject: 2.6.5-pre TCP connect problems
Date: Mon, 29 Mar 2004 15:50:42 +0200 [thread overview]
Message-ID: <20040329135042.GG2992@suse.de> (raw)
Hi,
I'm currently debugging a problem with TCP reconnects in 2.6.5-pre where
the TCP reconnect code got rewritten to use worker queues. What happens
is that the NFS server drops the connection immediately and that state
change isn't propagated to the transport. The typical sequence of
events goes like this
Mar 29 15:44:00 e36 kernel: RPC: 28611 call_transmit (status 0)
Mar 29 15:44:00 e36 kernel: RPC: 28611 xprt_prepare_transmit
Mar 29 15:44:00 e36 kernel: RPC: 28611 call_status (status -107)
Mar 29 15:44:00 e36 kernel: RPC: 28611 call_bind xprt d42c4200 is not connected
Mar 29 15:44:00 e36 kernel: RPC: 28611 call_connect status 0
Mar 29 15:44:00 e36 kernel: RPC: 28611 xprt_connect xprt d42c4200 is not connected
Mar 29 15:44:00 e36 kernel: RPC: disconnected transport d42c4200
Mar 29 15:44:00 e36 kernel: RPC: xprt_create_socket(tcp 6)
Mar 29 15:44:00 e36 kernel: RPC: d42c4200 connect status 115 connected 0 sock state 2
Mar 29 15:44:00 e36 kernel: RPC: tcp_state_change client d42c4200...
Mar 29 15:44:00 e36 kernel: RPC: state 1 conn 0 dead 0 zapped 0
Mar 29 15:44:00 e36 kernel: RPC: tcp_state_change client d42c4200...
Mar 29 15:44:00 e36 kernel: RPC: state 8 conn 1 dead 0 zapped 0
Mar 29 15:44:00 e36 kernel: RPC: disconnected transport d42c4200
Mar 29 15:44:00 e36 kernel: RPC: tcp_data_ready...
Mar 29 15:44:15 e36 kernel: RPC: 28611 call_transmit (status 0)
Mar 29 15:44:15 e36 kernel: RPC: 28611 xprt_prepare_transmit
Mar 29 15:44:15 e36 kernel: RPC: 28611 call_status (status -107)
Does this sound familiar to anyone?
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-03-29 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 13:50 Olaf Kirch [this message]
2004-03-29 15:28 ` 2.6.5-pre TCP connect problems Olaf Kirch
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=20040329135042.GG2992@suse.de \
--to=okir@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.