From: Tomasz Chmielewski <tch@virtall.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
b11g <b11g@protonmail.com>,
Andrea Gelmini <andrea.gelmini@gmail.com>
Subject: Re: BTRFS corruption: open_ctree failed
Date: Thu, 03 Jan 2019 16:43:20 +0900 [thread overview]
Message-ID: <b5df9ec049da6ecd9a4b3617d39d795f@virtall.com> (raw)
In-Reply-To: <20190103072740.GA64625@glet>
On 2019-01-03 16:27, Andrea Gelmini wrote:
> On Thu, Jan 03, 2019 at 11:52:05AM +0900, Tomasz Chmielewski wrote:
>> Did you use 4.19.x kernels earlier than 4.19.8?
>>
>> They had a bug which would corrupt filesystems (mostly ext4 users
>> would be
>> reporting it, but I saw it with other filesystems, like xfs and btrfs,
>> too):
>
> Well, just for the record, it triggers when you have
> scsi devices using elevator=none over blkmq.
>
> And it's not a default/usual configuration.
Still - it is a default configuration for some distributions. I.e.
Ubuntu "ppa" kernels[1] have this enabled by default (at least 4.19.x
and 4.20.x).
[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2019-01-03 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 2:52 BTRFS corruption: open_ctree failed Tomasz Chmielewski
2019-01-03 7:27 ` Andrea Gelmini
2019-01-03 7:43 ` Tomasz Chmielewski [this message]
2019-01-03 8:22 ` Andrea Gelmini
2019-01-03 8:29 ` Tomasz Chmielewski
2019-01-03 9:46 ` Andrea Gelmini
2019-01-03 14:32 ` b11g
-- strict thread matches above, loose matches on Subject: below --
2019-01-03 0:26 b11g
2019-01-03 4:52 ` Chris Murphy
2019-01-03 13:55 ` b11g
2019-01-11 12:29 ` b11g
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=b5df9ec049da6ecd9a4b3617d39d795f@virtall.com \
--to=tch@virtall.com \
--cc=andrea.gelmini@gelma.net \
--cc=andrea.gelmini@gmail.com \
--cc=b11g@protonmail.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox