From: Chris Mason <clm@fb.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Linux-next regression?
Date: Tue, 4 Dec 2018 22:29:49 +0000 [thread overview]
Message-ID: <FEDBF117-C83C-4DEC-96D1-A549DBCF4950@fb.com> (raw)
In-Reply-To: <20181128160523.GA5288@glet>
On 28 Nov 2018, at 11:05, Andrea Gelmini wrote:
> On Tue, Nov 27, 2018 at 10:16:52PM +0800, Qu Wenruo wrote:
>>
>> But it's less a concerning problem since it doesn't reach latest RC,
>> so
>> if you could reproduce it stably, I'd recommend to do a bisect.
>
> No problem to bisect, usually.
> But right now it's not possible for me, I explain further.
> Anyway, here the rest of the story.
>
> So, in the end I:
> a) booted with 4.20.0-rc4
> b) updated backup
> c) did the btrfs check --read-only
> d) seven steps, everything is perfect
> e) no complains on screen or in logs (never had)
> f) so, started to compile linux-next 20181128 (on another partition)
> e) without using (reading or writing) on /home, I started
> f) btrfs filesystem defrag -v -r -t 128M /home
> g) it worked without complain (in screen or logs)
> h) then, reboot with kernel tag 20181128
> i) and no way to mount:
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.
-chris
next prev parent reply other threads:[~2018-12-04 22:30 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 [this message]
2018-12-05 10:59 ` Andrea Gelmini
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=FEDBF117-C83C-4DEC-96D1-A549DBCF4950@fb.com \
--to=clm@fb.com \
--cc=andrea.gelmini@gelma.net \
--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 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).