From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Trond.Myklebust@netapp.com
Subject: Re: nfsd deadlock, 2.6.36-rc3
Date: Wed, 8 Sep 2010 13:50:32 -0400 [thread overview]
Message-ID: <20100908175032.GA816@fieldses.org> (raw)
In-Reply-To: <4C87BF63.3070808@canonical.com>
On Wed, Sep 08, 2010 at 10:52:51AM -0600, Tim Gardner wrote:
> The solution appears to be to twiddle with
> /proc/sys/vm/min_free_kbytes and /proc/sys/vm/drop_caches, though
> I'm not sure this addresses the root cause. Perhaps low memory
> really is the root cause.
>
> At any rate, their solution was to set min_free_kbytes to 4GB, and
> to 'echo 1 > /proc/sys/vm/drop_caches' whenever free memory fell
> below 8GB. Not particularly elegant, but it appears to have stopped
> their server from wedging.
That does sound like a workaround rather than a fix. Were there any
diagnostics left in the logs after the lockups? Could you get sysrq-t
dumps and figure out what was waiting on what? If the system was too
wedged for any of that to work, would any fo the watchdog deubgging
options help?
--b.
next prev parent reply other threads:[~2010-09-08 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 15:39 nfsd deadlock, 2.6.36-rc3 Tim Gardner
2010-09-01 16:54 ` J. Bruce Fields
2010-09-01 20:55 ` Neil Brown
2010-09-01 21:05 ` J. Bruce Fields
2010-09-01 21:11 ` Tim Gardner
2010-09-01 21:13 ` J. Bruce Fields
2010-09-02 15:13 ` Tim Gardner
2010-09-08 16:52 ` Tim Gardner
2010-09-08 17:50 ` J. Bruce Fields [this message]
2010-09-03 19:12 ` Maciej Rutecki
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=20100908175032.GA816@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tim.gardner@canonical.com \
/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.