linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Heinlein <aheinlein@gmx.com>
To: linux-nfs@vger.kernel.org
Subject: Kernel NFSd CPU hog?
Date: Mon, 02 Jul 2012 11:43:48 +0200	[thread overview]
Message-ID: <4FF16D54.6090200@gmx.com> (raw)

Hello,

we have a strange NFS problem with a newly setup Linux server, and I 
hope someone here can help.

The symptom is that, slowly over time (speaking of several days up to 2 
weeks), the kernel nfsd processes/threads consume more and more CPU 
until the system finally becomes unresponsive. We recorded system 
activity with sar, which shows that CPU (system) usage slowly rises 
after reboot from about 1% to nearly 100% over the course of several 
days. Load averages stay around 0.1-0.3 until 100% are reached, up to 
this point the problem is almost not noticable from the clients. Then 
load averages climb up to 30.0; at this point the system becomes more or 
less unusable and has to be restarted. 'top' output shows the CPU usage 
evenly distributed across all nfsd threads.

The system is a fairly recent, though entry level server with a Core i3 
and 4G RAM, hosting the home directories for about 15-20 clients. CPU 
activity does not drop at night, when no clients are connected. It is 
running Debian 6.0 with linux 3.2.0 (from the backports repository), 
with nfs-utils 1.2.5 (also from the backports repository). I suspect 
that these backports might be the culprit, but since we need this kernel 
for other purposes, and I cannot reboot that machine during office 
hours, I'd rather not try going back to the official Debian kernel 
without good reasons. If there are known problems, I'd give it a try.

Can anyone help me?

Thanks,
Andreas

             reply	other threads:[~2012-07-02  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02  9:43 Andreas Heinlein [this message]
2012-07-02 19:07 ` Kernel NFSd CPU hog? Jeff Layton
2012-07-03 12:35   ` Andreas Heinlein
2012-07-05 22:32     ` J. Bruce Fields
2012-08-24 20:29     ` J. Bruce Fields

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=4FF16D54.6090200@gmx.com \
    --to=aheinlein@gmx.com \
    --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;
as well as URLs for NNTP newsgroup(s).