From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Andrew Carr <andrewlanecarr@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Fwd: XFS Memory allocation deadlock in kmem_alloc
Date: Sat, 16 Nov 2019 10:43:33 +1100 [thread overview]
Message-ID: <20191115234333.GP4614@dread.disaster.area> (raw)
In-Reply-To: <e6222784-03a5-6902-0f2e-10303962749c@sandeen.net>
On Fri, Nov 15, 2019 at 01:52:57PM -0600, Eric Sandeen wrote:
> On 11/15/19 1:11 PM, Andrew Carr wrote:
> > Hello,
> >
> > This list has recommended enabling stack traces to determine the root
> > cause of issues with XFS deadlocks occurring in Centos 7.7
> > (3.10.0-1062).
> >
> > Based on what was recommended by Eric Sandeen, we have tried updating
> > the following files to generate XFS stack traces:
> >
> > # echo 11 > /proc/sys/fs/xfs/error_level
> >
> > And
> >
> > # echo 3 > /proc/sys/fs/xfs/error_level
> >
> > But no stack traces are printed to dmesg. I was thinking of
> > re-compiling the kernel with debug flags enabled. Do you think this
> > is necessary?
dmesg -n 7 will remove all filters on the console/dmesg output - if
you've utrned this down in the past you may not be seeing messages
of the error level XFS is using...
Did you check syslog - that should have all the unfiltered messages
in it...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-11-15 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKQeeLMxJR-ToX5HG9Q-z0-AL9vZG-OMjHyM+rnEEBP6k6nxHw@mail.gmail.com>
2019-11-15 19:11 ` Fwd: XFS Memory allocation deadlock in kmem_alloc Andrew Carr
2019-11-15 19:52 ` Eric Sandeen
2019-11-15 23:43 ` Dave Chinner [this message]
2019-11-16 16:19 ` Andrew Carr
2019-11-19 15:49 ` Andrew Carr
2019-11-19 20:20 ` Dave Chinner
2019-11-20 15:43 ` Andrew Carr
2019-11-22 14:08 ` Andrew Carr
2019-11-22 16:12 ` Darrick J. Wong
[not found] ` <CAC752A=7x+gh9Jr8-koQtuZDvMzrs6qRc+saj=TMC3js9EdHbg@mail.gmail.com>
2019-11-22 18:49 ` Darrick J. Wong
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=20191115234333.GP4614@dread.disaster.area \
--to=david@fromorbit.com \
--cc=andrewlanecarr@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).