From: Emmanuel Lacour <elacour@easter-eggs.com>
To: xfs@oss.sgi.com
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
Date: Mon, 9 Dec 2013 10:47:15 +0100 [thread overview]
Message-ID: <20131209094715.GC5821@easter-eggs.com> (raw)
In-Reply-To: <20131203125057.GU10988@dastard>
On Tue, Dec 03, 2013 at 11:50:57PM +1100, Dave Chinner wrote:
>
thanks very much for your quick and detailled answer!
> OK, 32GB RAM, no obvious shortage, no dirty or writeback data.
> 2TB SATA drives, 32AGs, only unusual setting is 64k directory block
> size.
>
yes, the 64k was taken from a too quickly read of advice, I don't think
it's of any help on a ceph cluster but I'm not an FS guru. Is there a
way to lower it at runtime?
> Yup, there's your problem:
>
[...]
> Which, I think, is pretty easy to do. Yup, barely smoke tested patch
> below that demonstrates the fix. Beware - patch may eat babies and
> ask for more. Use it at your own risk!
>
unfortunatly I cannot test this patch because:
- it's a production cluster and it's currently hard for me to reboot
nodes (not enough nodes ;))
- just after hiting this problem I saw a kernel 3.11 available on Debian
backports and decided to upgrade the whole cluster.
since this upgrade, there is no problems anymore ... I cross my fingers
;)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-09 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 9:13 XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250) Emmanuel Lacour
2013-11-28 10:05 ` Dave Chinner
2013-12-03 9:53 ` Emmanuel Lacour
2013-12-03 12:50 ` Dave Chinner
2013-12-03 16:28 ` Yann Dupont
2013-12-09 9:47 ` Emmanuel Lacour [this message]
2013-12-11 20:22 ` Ben Myers
2013-12-11 23:53 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2013-08-21 15:24 Josef 'Jeff' Sipek
2013-08-22 2:25 ` Dave Chinner
2013-08-22 15:07 ` Josef 'Jeff' Sipek
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=20131209094715.GC5821@easter-eggs.com \
--to=elacour@easter-eggs.com \
--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