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 10:31:48 +0900	[thread overview]
Message-ID: <YEV+hDZcguma9Pqg@burischnitzel.preining.info> (raw)
In-Reply-To: <CAJCQCtTn_O8grH5OBHoDfN7OfEOq5WM2Ryxffb-Z=qhVn_PLTg@mail.gmail.com> <CAJCQCtSZGGVamOUGRFzPXBejTW9Hx-2EkYUSCXdN6qEY3snW2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]

Hi Chris,

thanks a lot for your email!

> Post the photo? This is a generic message and we need to see more
> information. Is devid 9 missing?

Yes it is missing. I attach the screenshot.

> Does the initrd on this system contain?
>   /usr/lib/udev/rules.d/64-btrfs.rules

Good question, I don't have access now since I am doing the 
	btrfsck --check-data-csum
which takes a bit of time. On a similar system (but without multiple
disks and no raid), but otherwise the same Debian/sid, I don't have
the rules file in the initrd (only in /lib/udev/rules.d/64-btrfs.rules
on the running system)

> That will wait until all devices are available before attempting to
> mount. If it's not in the initrd, it won't wait and it's prone to
> races, and you can often get mount failures because not all devices
> are ready to be mounted.

Ahh, ok that could be an issue - I will try to include the udev rules
and try again with 5.11.4. Strange that it didn't before, though.

> This seems to be a somewhat risky setup or at least highly performance
> variable. Any single device that fails will result in boot failure.

I had that, and it can normally be easily recovered via mounting in
degraded mode, removing or replacing the device, and reboot.
Worked last time ;-) What would your suggestion be instead?

> > hangs are fixed). Now I read that -rc1 is a btrfs-killer. I have swap

> That bug should not have affected the dedication swap partition case.

Good to hear, thanks!

Best

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

[-- Attachment #2: boot-error-btrfs.jpg --]
[-- Type: image/jpeg, Size: 351571 bytes --]

  reply	other threads:[~2021-03-08  1:32 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 [this message]
2021-03-08  2:18     ` Norbert Preining
2021-03-08  2:34       ` Chris Murphy
2021-03-08  2:48         ` Norbert Preining
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=YEV+hDZcguma9Pqg@burischnitzel.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