From: Just Marc <marc-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Cc: bfields@fieldses.org
Subject: Re: lockd using up 60% CPU and won't let go
Date: Mon, 29 Sep 2008 20:18:10 -0400 [thread overview]
Message-ID: <48E17042.101@corky.net> (raw)
Hi,
> It's basically just a userspace NFS server, right?
Correct.
> Could you work around the problem by mounting with -onolock?
That doesn't seem to help.
>You might try running wireshark on the "lo" interface and seeing
whether there's any NLM traffic from lockd.
You guessed right. There's a 12 megabytes per second of NLM traffic on lo.
unlock call requests and unlock replies saying permission denied, looks
like it just repeats forever in a tight loop.
Marc
next reply other threads:[~2008-09-30 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 0:18 Just Marc [this message]
[not found] ` <48E17042.101-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
2008-09-30 12:25 ` lockd using up 60% CPU and won't let go Trond Myklebust
2008-09-30 18:26 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 16:46 Just Marc
[not found] ` <48E10657.7020503-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
2008-09-29 17:14 ` 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=48E17042.101@corky.net \
--to=marc-ztwyiuj8jqneowh0uzbu5w@public.gmane.org \
--cc=bfields@fieldses.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