From: Just Marc <marc-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: lockd using up 60% CPU and won't let go
Date: Mon, 29 Sep 2008 12:46:15 -0400 [thread overview]
Message-ID: <48E10657.7020503@corky.net> (raw)
Hi everyone,
Doing a seemingly innocent operation such as opening a file with vim on
a CFS (yes, that old crypto file system) NFS mount, lockd would wake up
and take 60% of my CPU away - probably doing nothing important but
certainly keeping the CPU busy, forever.
I use kernel 2.6.26 and kernel NFS. Some detail is available below:
$ grep nfs /proc/mounts
nfsd /proc/fs/nfsd nfsd rw 0 0localhost:/var/lib/cfs/.cfsfs /var/cfs nfs
rw,vers=2,rsize=8192,wsize=8192,namlen=255,hard,intr,proto=udp,timeo=11,retrans=3,sec=sys,addr=127.0.0.1
0 0
localhost:/var/lib/cfs/.cfsfs/x /var/cfs/x nfs
rw,vers=2,rsize=8192,wsize=8192,namlen=255,hard,intr,proto=udp,timeo=11,retrans=3,sec=sys,addr=127.0.0.1
0 0
$ egrep 'NFS|_LOCKD' .config
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
I noticed this a few weeks ago but I don't quite know what causes it but
I certainly know how to trigger it. Stopping CFS and NFS completely
doesn't help - as soon as NFS is restarted lockd starts eating CPU again
just like before.
I'd appreciate any hints on what I can do to find the root cause of the
problem and help get this bug out of the way.
Best,
Marc
next reply other threads:[~2008-09-29 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 16:46 Just Marc [this message]
[not found] ` <48E10657.7020503-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
2008-09-29 17:14 ` lockd using up 60% CPU and won't let go J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 0:18 Just Marc
[not found] ` <48E17042.101-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
2008-09-30 12:25 ` Trond Myklebust
2008-09-30 18:26 ` 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=48E10657.7020503@corky.net \
--to=marc-ztwyiuj8jqneowh0uzbu5w@public.gmane.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 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.