From: Helge Deller <deller@gmx.de>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>,
NFS list <linux-nfs@vger.kernel.org>,
list parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU?
Date: Thu, 17 Oct 2013 22:42:17 +0200 [thread overview]
Message-ID: <52604BA9.20104@gmx.de> (raw)
I'm seeing a regression with current kernel git head when using NFS-mounts.
Architecture in my case is parisc, although I don't think that this is relevant.
At least kernel 3.10 (and I think 3.11) didn't showed that problem.
The symtom is, that "top" shows high usage of either kswapd0 or kswapd1.
Here is an output with kswapd1:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
37 root 20 0 0 0 0 R 91.8 0.0 63:00.40 kswapd1
28448 root 20 0 3252 1428 1060 R 15.3 0.0 0:00.09 top
1 root 20 0 2784 988 852 S 0.0 0.0 0:09.95 init
This is what ps shows:
lsXXXX:~# ps -ef | grep mount
root 1181 1 0 14:51 ? 00:00:18 /usr/sbin/automount --pid-file /var/run/autofs.pid
root 25331 1181 0 21:25 ? 00:00:00 /bin/mount -n -t nfs -s -o nolock,rw,hard,intr homes:/unixhome1 /net/home1
root 25332 25331 0 21:25 ? 00:00:00 /sbin/mount.nfs homes:/unixhome1 /net/home1 -s -n -o rw,nolock,hard,intr
And using sysrq to show the blocked tasks I get in syslog:
SysRq : Show Blocked State
mount.nfs D 00000000401040c0 0 25332 25331 0x00000010
Backtrace:
[<0000000040113a68>] __schedule+0x500/0x810
I know it's not a problem of the NFS server, since the same mount is still ok on other machines.
The NFS directory was already mounted and in use when this mount happened again (called by cron-job).
Any ideas?
Helge
next reply other threads:[~2013-10-17 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 20:42 Helge Deller [this message]
2013-10-17 21:07 ` 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU? Myklebust, Trond
2013-10-18 19:26 ` Helge Deller
2013-10-18 19:36 ` Myklebust, Trond
2013-10-18 20:03 ` Helge Deller
2013-10-18 20:12 ` Myklebust, Trond
2013-10-19 18:27 ` Helge Deller
2013-10-31 19:45 ` Helge Deller
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=52604BA9.20104@gmx.de \
--to=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.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).