public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Meier <michael.meier@fau.de>
To: xfs@oss.sgi.com
Subject: Re: XFS hangs with XFS: possible memory allocation deadlock in kmem_alloc
Date: Sat, 07 Mar 2015 20:14:49 +0100	[thread overview]
Message-ID: <54FB4E29.7080705@fau.de> (raw)
In-Reply-To: <20150307140721.GA9098@bfoster.bfoster>

On 03/07/2015 03:07 PM, Brian Foster wrote:
> Thanks for the data. Some notes from the backtraces in the first
> instance:

Thank you for the quick reply.
I'm not sure if the first instance is the most representative: It was
very short - only one message was logged and then everything was fine
again. The later one starting at 00:48 in the logs however was long
enough to make our nagios complain.

> Considering this is a large memory box (64g), I wonder if some vm tuning
> might help mitigate this behavior..? For example, increase
> /proc/sys/vm/min_free_kbytes in hopes of allowing more memory for these
> allocations when under pressure, or tune down the
> dirty_ratio/dirty_background_ratio thresholds to more aggressively get
> data onto disk..?

That idea had occoured to me too, but at least
vm.min_free_kbytes=4000000
vm.vfs_cache_pressure=200
did not prevent the problem from occouring.

Regards,
-- 
Michael Meier, Zentrale Systeme
Friedrich-Alexander-Universitaet Erlangen-Nuernberg
Regionales Rechenzentrum Erlangen
Martensstrasse 1, 91058 Erlangen, Germany
Tel.: +49 9131 85-28973, Fax: +49 9131 302941
michael.meier@fau.de
www.rrze.fau.de

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-03-07 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  7:51 XFS hangs with XFS: possible memory allocation deadlock in kmem_alloc Michael Meier
2015-03-07 14:07 ` Brian Foster
2015-03-07 19:14   ` Michael Meier [this message]
2015-03-09 11:52   ` Dave Chinner

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=54FB4E29.7080705@fau.de \
    --to=michael.meier@fau.de \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox