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: Tue, 3 Dec 2013 10:53:58 +0100 [thread overview]
Message-ID: <20131203095357.GC5405@easter-eggs.com> (raw)
In-Reply-To: <20131128100521.GO10988@dastard>
On Thu, Nov 28, 2013 at 09:05:21PM +1100, Dave Chinner wrote:
> On Thu, Nov 28, 2013 at 10:13:22AM +0100, Emmanuel Lacour wrote:
> >
> > Dear XFS users,
> >
> >
> > I run a Ceph cluster using XFS on Debian wheezy servers and Linux 3.10
> > (debian backports). I see the following line in our logs:
> >
> > XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
> >
> > does this reveal a problem in my setup or may I ignore it? If it's a
> > problem, can someone give me any hint on solving this?
>
> It might be, but you need to provide more information for us to be
> able to make any intelligent comment on the message. Start here:
>
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
>
The problem continue and crashed my ceph cluster again, so here is all
the informations said in the FAQ:
http://people.easter-eggs.org/~manu/xfs.log
This may be related to a friend problem here:
http://tracker.ceph.com/issues/6386
thanks for any help on solving this!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-03 9:54 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 [this message]
2013-12-03 12:50 ` Dave Chinner
2013-12-03 16:28 ` Yann Dupont
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=20131203095357.GC5405@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