From: Tomasz Chmielewski <tch@virtall.com>
To: Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>, b11g <b11g@protonmail.com>
Subject: Re: BTRFS corruption: open_ctree failed
Date: Thu, 03 Jan 2019 17:29:51 +0900 [thread overview]
Message-ID: <ec02023516764c490fdb2fad5f409da5@virtall.com> (raw)
In-Reply-To: <20190103082213.GA74697@glet>
On 2019-01-03 17:22, Andrea Gelmini wrote:
> On Thu, Jan 03, 2019 at 04:43:20PM +0900, Tomasz Chmielewski wrote:
>> > 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).
>
> a) he is not using Ubuntu;
> b) I use this PPA;
> c) if you look at the config, you see the default scheduler is not
> "none", also
> the mq is compiled as module and - anyway - on release with the bug
> you have to
> force the kernel to use it with boot parameter.
Hmmm, is it the case?
# uname -r
4.20.0-042000-generic
# cat /sys/block/sda/queue/scheduler
[none]
# cat /sys/block/sdb/queue/scheduler
[none]
I could see filesystem corruption on every system using with PPA 4.19
lower than .8. Didn't do any kernel boot parameter changes when
upgrading from 4.18.
next prev parent reply other threads:[~2019-01-03 8:29 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
2019-01-03 8:22 ` Andrea Gelmini
2019-01-03 8:29 ` Tomasz Chmielewski [this message]
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=ec02023516764c490fdb2fad5f409da5@virtall.com \
--to=tch@virtall.com \
--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;
as well as URLs for NNTP newsgroup(s).