From: "S." <sb56637@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Upgraded from Buster to Bullseye, unmountable Btrfs filesystem
Date: Tue, 9 Nov 2021 21:55:20 -0500 [thread overview]
Message-ID: <37379516-cc7c-b045-ad2e-15c669a60921@gmail.com> (raw)
In-Reply-To: <a979e8db-f86a-dd3a-6f0a-588b14bbd97f@gmail.com>
Hi Qu, thank you very much for your fast response!
Regarding memtest, normally in Linux I have never been able to run it from inside an installed Linux system because it needs access to protected kernel memory, and instead it has to run from a live USB or from the memtest86 live testing image. But since this system is a proprietary NAS with uboot and no video interface I don't know how to run a memtest.
> To be extra safe, please provide the dump of your UUID tree:
------------------
root@OpenMediaVault:~# btrfs ins dump-tree -t uuid /dev/sda3
btrfs-progs v5.10.1
uuid tree key (UUID_TREE ROOT_ITEM 0)
leaf 170459136 items 4 free space 16151 generation 366 owner UUID_TREE
leaf 170459136 flags 0x1(WRITTEN) backref revision 1
fs uuid 4a057760-998c-4c66-aa6a-2a08c51d5299
chunk uuid 54b2fa0f-9907-49d1-af33-e172581cd25e
item 0 key (1101835439474057344 EXTENT_ITEM 56168916570538915) itemoff 16275 itemsize 8
item 1 key (0x0f4a817e92c9a080 UUID_KEY_SUBVOL 0xc78d54ff9b03a3a8) itemoff 16267 itemsize 8
subvol_id 5
item 2 key (0x421cfa6924ef510d UUID_KEY_SUBVOL 0xc8423812cf31288b) itemoff 16259 itemsize 8
subvol_id 269
item 3 key (0x45a64f82bc9152f1 UUID_KEY_SUBVOL 0x3859efe8688d6ea4) itemoff 16251 itemsize 8
subvol_id 274
total bytes 1990110658560
bytes used 704343715840
uuid 4a057760-998c-4c66-aa6a-2a08c51d5299
------------------
next prev parent reply other threads:[~2021-11-10 2:55 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. [this message]
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.
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=37379516-cc7c-b045-ad2e-15c669a60921@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