Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Norbert Preining <norbert@preining.info>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	Wang Yugui <wangyugui@e16-tech.com>
Subject: Re: btrfs fails to mount on kernel 5.11.4 but works on 5.10.19
Date: Mon, 8 Mar 2021 11:48:11 +0900	[thread overview]
Message-ID: <YEWQa2TXhdSbyWlR@bulldog.preining.info> (raw)
In-Reply-To: <CAJCQCtRmQ115LStiWXp2ihe-v8bvM+mUirMkBYGgu9EzbWpXCw@mail.gmail.com>

Hi Chris,

On Sun, 07 Mar 2021, Chris Murphy wrote:
> I suspect something is wrong with devid 9 in that case. If it's a
> dracut system, then it waits indefinitely for sysroot. You'll need to
> boot with something like rd.break=pre-mount and see first if you can
> mount normally to /sysroot, but if devid 9 is still missing then mount
> degraded and replace that device. Or otherwise find out why it's
> missing.

Ok, I will see what I can do. It isn't a dracut system, but
initramfs-tools AFAIS (not that I ever touched or decided anything in
this respect).

I will try to get to that state. (Only that USB devices seem to be hosed
in Debian's initramfs ... no kbd atm :-(

As said, it is just puzzling that 5.10.19 boots without a hinch and
without a warning, just running it now.

> I don't think the scrub helps right now, the issue is the device is

Ok, I have already killed it ;-)

Thanks a lot

Norbert

--
PREINING Norbert                              https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

  reply	other threads:[~2021-03-08  2:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 22:49 btrfs fails to mount on kernel 5.11.4 but works on 5.10.19 Norbert Preining
2021-03-08  0:16 ` Wang Yugui
2021-03-08  0:25   ` Norbert Preining
2021-03-08  1:06     ` Chris Murphy
2021-03-08  1:03 ` Chris Murphy
2021-03-08  1:31   ` Norbert Preining
2021-03-08  2:18     ` Norbert Preining
2021-03-08  2:34       ` Chris Murphy
2021-03-08  2:48         ` Norbert Preining [this message]
2021-03-08  3:50           ` [SOLVED] " Norbert Preining

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=YEWQa2TXhdSbyWlR@bulldog.preining.info \
    --to=norbert@preining.info \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=wangyugui@e16-tech.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