From: Dave Chinner <david@fromorbit.com>
To: Cyril Peponnet <cyril.peponnet@nuagenetworks.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc on glusterfs setup
Date: Mon, 5 Dec 2016 08:49:50 +1100 [thread overview]
Message-ID: <20161204214950.GL31101@dastard> (raw)
In-Reply-To: <E861E5C1-D1C2-4368-8BFC-505533C9A3A3@nuagenetworks.net>
On Sat, Dec 03, 2016 at 11:08:58AM -0800, Cyril Peponnet wrote:
> Hi xfs community :),
>
> We have a glusterfs setup running under centos7.2. We are using
> xfs as underlying storage for the bricks. The volume is used to
> store vm snapshots that’s gets created dynamically from the
> hypervisors through glusterfs mount points.
>
> While this is working fine we have some issues from time to time
> that make the mount points hang.
>
> We have the famous XFS: possible memory allocation deadlock in
> kmem_alloc (mode:0x250) errors appearing from time to time on some
> of our gluster nodes.
And the complete output in dmesg is?
> Let me know if you need more information about our systems (like
> kernel version, underlying storage…)
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-12-04 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:08 XFS: possible memory allocation deadlock in kmem_alloc on glusterfs setup Cyril Peponnet
2016-12-04 21:49 ` Dave Chinner [this message]
2016-12-04 22:07 ` Cyril Peponnet
2016-12-04 22:46 ` Dave Chinner
2016-12-04 23:24 ` Cyril Peponnet
2016-12-04 23:50 ` Dave Chinner
2016-12-05 1:14 ` Cyril Peponnet
2016-12-05 1:22 ` Dave Chinner
2016-12-05 1:48 ` Cyril Peponnet
[not found] ` <C07DD929-5600-4934-A6B0-C0A7D83D7247@nuagenetworks.net>
2016-12-05 7:46 ` Dave Chinner
2016-12-05 15:51 ` Cyril Peponnet
2016-12-05 21:45 ` Dave Chinner
2016-12-06 17:54 ` Cyril Peponnet
2016-12-07 6:16 ` Dave Chinner
[not found] ` <473936408.4772.1481091425441@itfw6.prod.google.com>
[not found] ` <8176484246282250577@unknownmsgid>
2016-12-07 19:44 ` 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=20161204214950.GL31101@dastard \
--to=david@fromorbit.com \
--cc=cyril.peponnet@nuagenetworks.net \
--cc=linux-xfs@vger.kernel.org \
/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.