From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: Chris Mason <clm@fb.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Linux-next regression?
Date: Wed, 5 Dec 2018 11:59:28 +0100 [thread overview]
Message-ID: <20181205105928.GA29665@glet> (raw)
In-Reply-To: <FEDBF117-C83C-4DEC-96D1-A549DBCF4950@fb.com>
On Tue, Dec 04, 2018 at 10:29:49PM +0000, Chris Mason wrote:
> I think (hope) this is:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=201685
>
> Which was just nailed down to a blkmq bug. It triggers when you have
> scsi devices using elevator=none over blkmq.
Thanks a lot Chris. Really.
Good news: I confirm I recompiled and used blkmq and no-op (at that time).
Also, the massive write of btrfs defrag can explain the massive trigger of
the bug, and next corruption.
Thanks again,
Andrea
next prev parent reply other threads:[~2018-12-05 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 15:01 Linux-next regression? Andrea Gelmini
2018-11-27 1:13 ` Qu Wenruo
2018-11-27 14:11 ` Andrea Gelmini
2018-11-27 14:16 ` Qu Wenruo
2018-11-28 16:05 ` Andrea Gelmini
2018-12-04 22:29 ` Chris Mason
2018-12-05 10:59 ` Andrea Gelmini [this message]
2018-12-05 19:32 ` Chris Mason
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=20181205105928.GA29665@glet \
--to=andrea.gelmini@gelma.net \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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 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.