Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Just Marc <marc-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
Cc: linux-nfs@vger.kernel.org, bfields@fieldses.org
Subject: Re: lockd using up 60% CPU and won't let go
Date: Tue, 30 Sep 2008 08:25:54 -0400	[thread overview]
Message-ID: <1222777554.7332.10.camel@localhost> (raw)
In-Reply-To: <48E17042.101-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>

On Mon, 2008-09-29 at 20:18 -0400, Just Marc wrote:
> 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.

As Bruce said, you need to mount with -onolock. Please unmount _all_
your cfs partitions, then mount them again with -onolock.

Note that -oremount,nolock will not work and for some kernels, mounting
while you have the same cfs partition mounted somewhere else will cause
the kernel to use the 'old' mount options.
See /proc/mounts to find out which mount options the kernel is actually
using.

Cheers
  Trond


  parent reply	other threads:[~2008-09-30 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30  0:18 lockd using up 60% CPU and won't let go Just Marc
     [not found] ` <48E17042.101-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.org>
2008-09-30 12:25   ` Trond Myklebust [this message]
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=1222777554.7332.10.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=marc-ZTWYIuj8JqNeoWH0uzbU5w@public.gmane.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