public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "S." <sb56637@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Upgraded from Buster to Bullseye, unmountable Btrfs filesystem
Date: Wed, 10 Nov 2021 09:01:34 -0500	[thread overview]
Message-ID: <c94ecfa2-752b-9952-9483-ae3dd04f6c02@gmail.com> (raw)
In-Reply-To: <76156d73-9d4c-a473-4dd2-105a905d3d1e@gmx.com>


On 11/10/21 02:01, Qu Wenruo wrote:
> If you can revert to older kernel/distro, then you can mount the fs with
> "-o rescan_uuid" to regenerate the UUID tree using the old kernel.
> 
> Then it would rebuild the UUID tree, no need for a tool in user space.

Thanks very much for the explanation and for the suggestions.
Fortunately the system saved a copy of the old 4.19 kernel and initrd image. You are correct that the old kernel can still boot the filesystem without errors. Then I unmounted it and remounted it with `-o rescan_uuid_tree`. This also appeared to work, as it was able to mount. However, after rebooting into the new Bullseye kernel the filesystem is still unmountable:

------------------------
[  115.250774] BTRFS info (device sda3): flagging fs with big metadata feature
[  115.257773] BTRFS info (device sda3): disk space caching is enabled
[  115.264089] BTRFS info (device sda3): has skinny extents
[  115.414229] BTRFS critical (device sda3): corrupt leaf: root=9 block=170459136 slot=0, invalid key objectid, have 1101835439474057344 expect to be aligned to 4096
[  115.428780] BTRFS error (device sda3): block=170459136 read time tree block corruption detected
[  115.459643] BTRFS critical (device sda3): corrupt leaf: root=9 block=170459136 slot=0, invalid key objectid, have 1101835439474057344 expect to be aligned to 4096
[  115.474296] BTRFS error (device sda3): block=170459136 read time tree block corruption detected
[  115.483109] BTRFS warning (device sda3): failed to read root (objectid=9): -5
[  115.534748] BTRFS error (device sda3): open_ctree failed
------------------------

Any more ideas? Thanks again.

  reply	other threads:[~2021-11-10 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  2:17 Upgraded from Buster to Bullseye, unmountable Btrfs filesystem S.
2021-11-10  2:33 ` Qu Wenruo
2021-11-10  2:55 ` S.
2021-11-10  3:34   ` Qu Wenruo
2021-11-10  4:30   ` S.
2021-11-10  7:01     ` Qu Wenruo
2021-11-10 14:01       ` S. [this message]
2021-11-10 23:46         ` Qu Wenruo
2021-11-11  0:18           ` S.
2021-11-11  0:58             ` Qu Wenruo
2021-11-11  2:29               ` S.
     [not found]               ` <e19518ec-a885-4a1d-1dda-a5be645a1d73@gmail.com>
     [not found]                 ` <73fb26b3-932c-9592-bced-6a3fda3456f0@gmx.com>
     [not found]                   ` <fdcac254-e169-7aba-7a12-c828aaab3231@gmail.com>
2021-11-12  0:06                     ` Qu Wenruo
2021-11-11  5:22         ` S.
2021-11-11  6:20           ` Rosen Penev
2021-11-11 14:26             ` S.
2021-11-12 15:18     ` S.

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=c94ecfa2-752b-9952-9483-ae3dd04f6c02@gmail.com \
    --to=sb56637@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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