All of lore.kernel.org
 help / color / mirror / Atom feed
From: b11g <b11g@protonmail.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: Tomasz Chmielewski <tch@virtall.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS corruption: open_ctree failed
Date: Thu, 03 Jan 2019 14:32:59 +0000	[thread overview]
Message-ID: <3bVsFicVvIyBXxe3CYYCVF_P99BjDh_iNNQpUHxA9gZMJJgG-0K5ttWn_JwQwvFrUBfHONWyp7ZQz6PkQpX2XdcnzzOSIxazRVQch0uCGYw=@protonmail.com> (raw)
In-Reply-To: <20190103072740.GA64625@glet>

I heard of the ext4 bug, but I didn't check my kernel more carefully - contrarily to what I reported previously, my kernel version was 4.14.79, NOT 4.19.12 (I think I installed the latter, but the system was still pending a reboot). I am sorry if this caused confusion.

AFAIK, those are the flags used in the NixOS kernel:
https://github.com/NixOS/nixpkgs/blob/0396345b79436f54920f7eb651ab42acf2eb7973/pkgs/os-specific/linux/kernel/common-config.nix
I did not find references to "elevator" nor "scsi_mod.use_blk_mq" there or in the boot command line.

-b11g

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 3 January 2019 08:27, Andrea Gelmini <andrea.gelmini@gelma.net> 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.
>
> So, b11g, can you check please if the NixOS kernel is compiled with these flags?
> And/or if they have something like:
> scsi_mod.use_blk_mq=1
> in the boot command line?
>
> Ciao,
> Gelma

  parent reply	other threads:[~2019-01-03 14:33 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
2019-01-03 14:32   ` b11g [this message]
  -- 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='3bVsFicVvIyBXxe3CYYCVF_P99BjDh_iNNQpUHxA9gZMJJgG-0K5ttWn_JwQwvFrUBfHONWyp7ZQz6PkQpX2XdcnzzOSIxazRVQch0uCGYw=@protonmail.com' \
    --to=b11g@protonmail.com \
    --cc=andrea.gelmini@gelma.net \
    --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 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.