From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>, b11g <b11g@protonmail.com>
Subject: Re: BTRFS corruption: open_ctree failed
Date: Thu, 3 Jan 2019 10:46:47 +0100 [thread overview]
Message-ID: <20190103094647.GA10578@glet> (raw)
In-Reply-To: <ec02023516764c490fdb2fad5f409da5@virtall.com>
My last email on this thread: I swear.
I don't want to bother the mailing list about this more.
On Thu, Jan 03, 2019 at 05:29:51PM +0900, Tomasz Chmielewski wrote:
> 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.
gelma@check:~$ uname -a # to use a broken kernel
Linux check 4.19.6-041906-generic #201812030857 SMP Mon Dec 3 13:59:30 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
gelma@check:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic
gelma@check:~$ dmesg|grep -i scheduler
[ 1.062769] io scheduler noop registered
[ 1.062993] io scheduler deadline registered
[ 1.063257] io scheduler cfq registered (default)
But also just having set "none" is not enough.
To trigger it you must force multiqueue.
I usually compile the git kernel, but I destroyed the
fs only when I added:
scsi_mod.use_blk_mq=1
on boot kernel.
Details here:
https://bugzilla.kernel.org/show_bug.cgi?id=201685
Ciao,
Gelma
next prev parent reply other threads:[~2019-01-03 9:46 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
2019-01-03 9:46 ` Andrea Gelmini [this message]
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=20190103094647.GA10578@glet \
--to=andrea.gelmini@gelma.net \
--cc=b11g@protonmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tch@virtall.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