mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kasparek Tomas <kasparek@fit.vutbr.cz>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS client packet storm on 2.6.27.x
Date: Wed, 29 Apr 2009 16:57:53 +0200	[thread overview]
Message-ID: <20090429145753.GL2865@fit.vutbr.cz> (raw)
In-Reply-To: <49F84436.5090007@RedHat.com>

On Wed, Apr 29, 2009 at 08:12:38AM -0400, Steve Dickson wrote:
> > I got another client lockup today. It was a desktop so I have some more
> > dmesg warnings about soft lockup caused probably by network cable unplug
> > (but hopefully still showing what happens in rpciod) on
> > 
> > http://merlin.fit.vutbr.cz/tmp/nfs/pckas-dmesg
> > 
> > I can check with top, that rpciod was using 100% cpu. I limited the flow
> > from client to server with firewall so I was able to save the server and
> > get some tcpdump -s0 data (actually RPC null with ERR response from server)
> > 
> > Just to remind, the client is 2.6.27.21 (i386), the server is 2.6.16.62
> > (x86_64).
> > 
> > Please let me know if I can do anything more, this is really paintfull for
> > me.
> Try commenting out the tcp6/udp6 entries from /etc/netconfig....
> This has help in other places...

It's CentOS 5.3, but if you mean to disable IPv6, I can not do that, the
server is using IPv6 (but not with these clients). And as mentioned before
it works well without e06799f958bf7f9f8fae15f0c6f519953fb0257c, both for
lockd and client floods.

Bye

--   

  Tomas Kasparek, PhD student  E-mail: kasparek@fit.vutbr.cz
  CVT FIT VUT Brno, L127       Web:    http://www.fit.vutbr.cz/~kasparek
  Bozetechova 1, 612 66        Fax:    +420 54114-1270
  Brno, Czech Republic         Phone:  +420 54114-1220

  jabber: tomas.kasparek@jabber.cz
  GPG: 2F1E 1AAF FD3B CFA3 1537  63BD DCBE 18FF A035 53BC


  reply	other threads:[~2009-04-29 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1231782009.7322.12.camel@heimdal.trondhjem.org>
     [not found] ` <1231809446.7322.17.camel@heimdal.trondhjem.org>
     [not found]   ` <20090113152201.GD47559@fit.vutbr.cz>
     [not found]     ` <20090116104802.GF47559@fit.vutbr.cz>
     [not found]       ` <20090118130835.GH47559@fit.vutbr.cz>
     [not found]         ` <20090120150301.GG47559@fit.vutbr.cz>
     [not found]           ` <1232465547.7055.3.camel@heimdal.trondhjem.org>
     [not found]             ` <20090303120848.GV89843@fit.vutbr.cz>
     [not found]               ` <1236089767.9631.4.camel@heimdal.trondhjem.org>
     [not found]                 ` <20090418051739.GL64731@fit.vutbr.cz>
2009-04-22 17:27                   ` Kasparek Tomas
2009-04-29 12:12                     ` Steve Dickson
2009-04-29 14:57                       ` Kasparek Tomas [this message]
2009-06-25  5:55                     ` Kasparek Tomas
2009-07-13 11:12                       ` Kasparek Tomas
2009-07-13 17:20                         ` [stable] " Greg KH
2009-07-13 17:40                           ` Trond Myklebust
2009-07-28 18:31                             ` Greg KH

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=20090429145753.GL2865@fit.vutbr.cz \
    --to=kasparek@fit.vutbr.cz \
    --cc=SteveD@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®