public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Skensved <peter@jay.phy.QueensU.CA>
To: linux-nfs@vger.kernel.org
Subject: nfsd4_stateowners problem
Date: Fri, 27 Aug 2010 13:48:23 -0400	[thread overview]
Message-ID: <20100827174823.GA26792@jay.phy.QueensU.CA> (raw)


  I'm looking for pointers and information on how to debug and annoying NFS
problem that has been bugging us for a long time. The problem is that the number
of nfsd4_stateowners keeps increasing until all low memory is exhausted and
the oom-killer is invoked. The severity of the problem has changed over time
with different kernels. At present it takes about 5 weeks for the size to
grow to 500 Mb  ( kernel 2.6.18-194.8.1.el5PAE, CentOS5.5 ). Restarting 
nfs clears up the problem but it is definitely not the preferred solution. 

 The increase in the number of nfsd4_stateowners appears to happen in bursts.
Nothing happens for long times and I suddenly see a burst. I've tried ( briefly )
to turn on all logging in rpcdebug and have run tcpdump while watching slabtop
but there is too much output to be able to see if there is anything strange
happening. So - my question is : how do I limit the diagnostic output to what
is relevant ? What are the modules and flags that I should be looking at ?
Any other info I should bemonitoring ? /proc/fs/nfsfs ?

                                                        peter
----

Peter Skensved                          Email : peter@SNO.Phy.QueensU.CA
Dept. of Physics,
Queen's University,
Kingston, Ontario,
Canada


             reply	other threads:[~2010-08-27 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 17:48 Peter Skensved [this message]
2010-09-14 17:31 ` nfsd4_stateowners problem J. Bruce Fields
2010-09-14 18:40   ` Peter Skensved
2010-09-14 20:00     ` J. Bruce Fields
2010-09-14 20:24       ` Peter Skensved

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=20100827174823.GA26792@jay.phy.QueensU.CA \
    --to=peter@jay.phy.queensu.ca \
    --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