From: Jacob Riddle <ironlenny@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Error: failed to read chunk root
Date: Thu, 24 Sep 2020 21:24:05 -0700 [thread overview]
Message-ID: <00fe2cbb-e5ef-72a9-9702-4992f1b5954e@gmail.com> (raw)
Information requested by
https://btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list:
> uname -a
Linux ranger 5.8.7-1-default #1 SMP Sun Sep 6 07:39:46 UTC 2020
(7fc52c0) x86_64 x86_64v x86_64 GNU/Linux
> btrfs --version
btrfs-progs v5.7
> btrfs fi show
Label: none uuid: 3570f55b-a52a-482f-9629-ba282cdd3ada
Total devices 1 FS bytes used 17.01GiB
devid 1 size 20.00GiB used 20.00GiB path /dev/nvme0n1p3
Label: none uuid: 9d1911ef-773e-4a73-978a-5814fcf46f68
Total devices 1 FS bytes used 870.93GiB
devid 1 size 1.82TiB used 874.08GiB path /dev/bcache0
> btrfs fi df /home # Replace /home with the mount point of your
btrfs-filesystem
Cannot provide for /home as filesystem is unmountable
> dmesg > dmesg.log
Error is in the body.
I am running OpenSUSE Tumbleweed. My home mount is a Bcache device with
BTRFS. I
did an update and restarted the computer. Everything seemed to be going
well,
untill KDE stopped loading. I switched to a virtual terminal to see what the
problem was. Upon logging in, I was presented with a stream of BTRFS
errors. I
don't remember what the errors were, as I prompltly forced the computer
down. I
booted into the recovery kernel, and tried doing `mount /home`. I now
get this
error:
[ 6.848351] BTRFS info (device bcache0): use zstd compression, level 3
[ 6.848352] BTRFS info (device bcache0): disk space caching is enabled
[ 6.848353] BTRFS info (device bcache0): has skinny extents
[ 6.848802] BTRFS error (device bcache0): bad tree block start, want
1129766191104 have 1123189522432
[ 6.848806] BTRFS error (device bcache0): failed to read chunk root
[ 6.884205] BTRFS error (device bcache0): open_ctree failed
mount: /home: wrong fs type, bad option, bad superblock on /dev/bcache0,
missing codepage or helper program, or other error.
Can I recover from this? If so, what steps do I need to take?
reply other threads:[~2020-09-25 4:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00fe2cbb-e5ef-72a9-9702-4992f1b5954e@gmail.com \
--to=ironlenny@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