From: "S." <sb56637@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Upgraded from Buster to Bullseye, unmountable Btrfs filesystem
Date: Fri, 12 Nov 2021 10:18:57 -0500 [thread overview]
Message-ID: <148e9643-7154-d5f6-ff95-34fc601bfa1f@gmail.com> (raw)
In-Reply-To: <179e61f7-82c9-0a5f-1a05-7c0019b4f126@gmail.com>
Here's an update and hopefully the conclusion to this thread:
Qu has been a huge help, and I really appreciate his time and patience. It was ultimately necessary for him to manually repair my tree block, since my NAS uses an old and obscure processor architecture. But in the end he sent me back a repaired tree block file with instructions to write it back out to my disks, and now the filesystem is working fine. Still no idea how this happened, as memtester doesn't find any issues. It's possible that I hit some weird 32-bit quirk, as I imagine that not a lot of people are running Btrfs RAID-1 on 32-bit systems. The good thing that came out of this is a new `clear-uuid-tree` function that Qu is proposing for btrfs-progs, so hopefully there will be an automated way to fix this weird error if it hits anybody in the future. Thanks again for the support!
prev parent reply other threads:[~2021-11-12 15:19 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.
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. [this message]
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=148e9643-7154-d5f6-ff95-34fc601bfa1f@gmail.com \
--to=sb56637@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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