From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: xfs@oss.sgi.com
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
Date: Tue, 03 Dec 2013 17:28:09 +0100 [thread overview]
Message-ID: <529E0699.4020601@univ-nantes.fr> (raw)
In-Reply-To: <20131203125057.GU10988@dastard>
Le 03/12/2013 13:50, Dave Chinner a écrit :
> On Tue, Dec 03, 2013 at 10:53:58AM +0100, Emmanuel Lacour wrote:
> OK, 32GB RAM, no obvious shortage, no dirty or writeback data. 2TB
> SATA drives, 32AGs, only unusual setting is 64k directory block size.
> Yup, there's your problem:
I can confirm I also saw this from times to times, in the very same
context (ceph OSD, xfs volume with 64k directory blocks)
I never took the time to fully report the problem because it was very
sporadic, and I suspected a specific option in my hand-made kernels, in
which the problem seems to occurs more often. With the 'standard'
debian 3.10.2 (from testing) I never saw the problem (56 days uptime)
cf http://tracker.ceph.com/issues/6301
the report isn't complete here ... sometimes I just have the deadlock,
but without oops.
can try to dig deeper inmy old logs to be sure it's really the same
Cheers,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-03 16:30 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 [this message]
2013-12-09 9:47 ` Emmanuel Lacour
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=529E0699.4020601@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--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