All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
Cc: Petr Vandrovec <petr@vandrovec.name>,
	Andrew Morton <akpm@linux-foundation.org>,
	khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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 16:58:56 -0400	[thread overview]
Message-ID: <1240433936.9197.9.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <200904222049.n3MKnxZi019947-jEpIWWs/U2wOASNP4CLbKB2eb7JE58TQ@public.gmane.org>

(Switching to bugzilla email interface, and ccing linux-nfs)

On Wed, 2009-04-22 at 20:49 +0000, bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13034
> 
> 
> 
> 
> 
> --- Comment #12 from Petr Vandrovec <petr@vandrovec.name>  2009-04-22 20:49:58 ---
> Unfortunately I have no access to the server (they are some NetApp and EMC
> storage devices maintained by company IT).
> 
> It seems that they are all configured same way, so after mount they start
> timing out connections all at the same moment (after 10 minutes since mount, or
> something like that), and netstat above is captured when I run 'df' after
> connections moved from established to time_wait on client side.  That TIME_WAIT
> disappear after 60 seconds, as expected.

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)...



       reply	other threads:[~2009-04-22 20:59 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     ` Trond Myklebust [this message]
     [not found]       ` <1240433936.9197.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-22 22:22         ` [Bug 13034] printk in xs_tcp_setup_socket needs rate limit ... and delay Petr Vandrovec
2009-04-23  0:52           ` Trond Myklebust
     [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=1240433936.9197.9.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 \
    /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.