From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: softlockup with CONFIG_XFS_ONLINE_SCRUB enabled
Date: Mon, 28 Oct 2019 08:30:03 +0100 [thread overview]
Message-ID: <20191028073003.GA20274@lst.de> (raw)
In-Reply-To: <20191027183232.GA15221@magnolia>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Sun, Oct 27, 2019 at 11:32:32AM -0700, Darrick J. Wong wrote:
> On Fri, Oct 25, 2019 at 12:24:04PM +0200, Christoph Hellwig wrote:
> > Hi Darrick,
> >
> > the current xfs tree seems to easily cause sotlockups in generic/175
> > (and a few other tests, but not as reproducible) for me. This is on
> > 20GB 4k block size images on a VM with 4 CPUs and 4G of RAM.
>
> Hrm. I haven't seen that before... what's your kernel config?
> This looks like some kind of lockup in slub debugging...?
>
> Also, is this a new thing? Or something that used to happen with low
> frequency but has slowly increased to the point that it's annoying?
>
> (Or something else?)
Seems to happen with 5.3 as well. I only recently turned
CONFIG_XFS_ONLINE_SCRUB back on in my usual test config, that is what
made it show up..
.config attached.
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 32546 bytes --]
next prev parent reply other threads:[~2019-10-28 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 10:24 softlockup with CONFIG_XFS_ONLINE_SCRUB enabled Christoph Hellwig
2019-10-27 18:32 ` Darrick J. Wong
2019-10-28 7:30 ` Christoph Hellwig [this message]
2019-10-29 3:58 ` 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=20191028073003.GA20274@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--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.