From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Petr Vandrovec <petr@vmware.com>
Cc: "bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org"
<bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org>,
Petr Vandrovec <petr@vandrovec.name>,
Andrew Morton <akpm@linux-foundation.org>,
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [Bug 13034] printk in xs_tcp_setup_socket needs rate limit ... and delay
Date: Wed, 22 Apr 2009 20:52:57 -0400 [thread overview]
Message-ID: <1240447977.9197.14.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <49EF9896.2000301@vmware.com>
On Wed, 2009-04-22 at 15:22 -0700, Petr Vandrovec wrote:
> Trond Myklebust wrote:
> > So these connections are basically timing out because the systems are
> > idle? (FYI: the NFS convention is that clients are supposed to close the
> > TCP connection if it has been idle for 5 minutes, whereas the servers
> > usually close it if the client has been idle for 6 minutes)...
>
> Yes, they are timing out because system is idle. It seems that it
> behaves way it should - it is client who closes them, 5 minutes after I
> run 'df':
Good! The 5minute idle timeout is the one case where we don't care about
preserving the port number (because there are no outstanding NFS
requests to replay to the server).
Jean, are you seeing the same behaviour (i.e. errors only on idle
timeout), and is the fix working for you?
next prev parent reply other threads:[~2009-04-23 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13034-104@http.bugzilla.kernel.org/>
[not found] ` <200904222049.n3MKnxZi019947@demeter.kernel.org>
[not found] ` <200904222049.n3MKnxZi019947-jEpIWWs/U2wOASNP4CLbKB2eb7JE58TQ@public.gmane.org>
2009-04-22 20:58 ` [Bug 13034] printk in xs_tcp_setup_socket needs rate limit ... and delay Trond Myklebust
[not found] ` <1240433936.9197.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-22 22:22 ` Petr Vandrovec
2009-04-23 0:52 ` Trond Myklebust [this message]
[not found] ` <1240447977.9197.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-23 7:02 ` Jean Delvare
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=1240447977.9197.14.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=petr@vmware.com \
/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.