From: Lee Fleming <leeflemingster@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Unbootable root btrfs
Date: Thu, 16 May 2019 11:36:54 +0100 [thread overview]
Message-ID: <CAKS=YrP=z2+rP5AtFKkf7epi+Dr2Arfsaq3pZ9cR3iKif3gV5g@mail.gmail.com> (raw)
After seeking advice on reddit I've been advised to post this problem
here. See https://www.reddit.com/r/btrfs/comments/bp0awe/broken_btrfs_filesystem_following_a_reboot/
I have a root btrfs filesystem on top of mdadm raid10 and lvm. The
raid and lvm appear to be ok but the btrfs partition will not mount.
I have booted a live recovery and tried to mount/repair the
filesystem. This is the result.
% mount /dev/mapper/vg-root /mnt/gentoo
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on
/dev/mapper/vg-root,
missing codepage or helper program, or other error.
Trying to mount with recovery gives the same result:
% mount -o ro,recovery /dev/mapper/vg-root /mnt/gentoo
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on
/dev/mapper/vg-root,
missing codepage or helper program, or other error.
And a btrfs check gives the following:
% btrfs check --repair /dev/mapper/vg-root
enabling repair mode
bytenr mismatch, want=898031484928, have=898006728704
ERROR: cannot open file system
% dmesg | grep -i btrfs [ 5.562419] Btrfs loaded, crc32c=crc32c-generic
[ 14.381989] BTRFS: device fsid
1fb019f1-a8cc-46ef-8122-ac6b1bedd522 devid 1 transid 51979 /dev/dm-1
[ 14.382647] BTRFS info (device dm-1): disk space caching is enabled
[ 14.382652] BTRFS info (device dm-1): has skinny extents
[ 15.777186] BTRFS error (device dm-1): bad tree block start 0 898031337472
[ 15.777334] BTRFS error (device dm-1): bad tree block start 0 898031353856
[ 15.777486] BTRFS error (device dm-1): bad tree block start 0 898031370240
[ 15.864239] BTRFS error (device dm-1): bad tree block start
898006728704 898031484928
[ 15.871367] BTRFS error (device dm-1): bad tree block start
898003812352 898031484928
[ 15.871382] BTRFS error (device dm-1): failed to read block groups: -5
[ 15.892051] BTRFS error (device dm-1): open_ctree failed
[ 16.016182] BTRFS info (device dm-1): disk space caching is enabled
[ 16.016186] BTRFS info (device dm-1): has skinny extents
[ 17.319016] BTRFS error (device dm-1): bad tree block start 0 898031337472
[ 17.319157] BTRFS error (device dm-1): bad tree block start 0 898031353856
[ 17.319303] BTRFS error (device dm-1): bad tree block start 0 898031370240
[ 17.422706] BTRFS error (device dm-1): bad tree block start
898006728704 898031484928
[ 17.429831] BTRFS error (device dm-1): bad tree block start
898003812352 898031484928
[ 17.429845] BTRFS error (device dm-1): failed to read block groups: -5
[ 17.450035] BTRFS error (device dm-1): open_ctree failed % uname
-r 4.14.70-std531-amd64
% wipefs /dev/mapper/vg-root
DEVICE OFFSET TYPE UUID LABEL
vg-root 0x10040 btrfs 1fb019f1-a8cc-46ef-8122-ac6b1bedd522
I was asked to try with a more recent kernel. I booted archiso which
showed similar results.
# uname -r
5.0.10-arch1-1-ARCH
# mount /dev/mapper/vg-root /mnt/funtoo
[ 208.724214] BTRFS error (device dm-1): bad tree block start,
want 898031337472 have 0
[ 208.724343] BTRFS error (device dm-1): bad tree block start,
want 898031353856 have 0
[ 208.724556] BTRFS error (device dm-1): bad tree block start,
want 898031370240 have 0
[ 208.805279] BTRFS error (device dm-1): bad tree block start,
want 898031484928 have 898006728704
[ 208.812412] BTRFS error (device dm-1): bad tree block strat,
want 898031484928 have 898003812352
[ 208.812451] BTRFS error (device dm-1): failed to read block groups: -5
[ 208.840576] BTRFS error (device dm-1): open_ctree failed
mount: /mnt/funtoo: wrong fs type, bad option, bad superblock on
/dev/mapper/vg-root, missing codepage or helper program, or other
error.
32
# dmesg|grep -i btrfs [ 23.028283] Btrfs loaded, crc32c=crc32c-intel
[ 23.061402] BTRFS: device fsid
1fb019f1-a8cc-46ef-8122-ac6b1bedd522 devid 1 transid 51979 /dev/dm-1
[ 207.437375] BTRFS info (device dm-1): disk space caching is enabled
[ 207.437379] BTRFS info (device dm-1): has skinny extents
[ 208.724214] BTRFS error (device dm-1): bad tree block start,
want 898031337472 have 0
[ 208.724343] BTRFS error (device dm-1): bad tree block start,
want 898031353856 have 0
[ 208.724556] BTRFS error (device dm-1): bad tree block start,
want 898031370240 have 0
[ 208.805279] BTRFS error (device dm-1): bad tree block start,
want 898031484928 have 898006728704
[ 208.812412] BTRFS error (device dm-1): bad tree block start,
want 898031484928 have 898003812352
[ 208.812451] BTRFS error (device dm-1): failed to read block groups: -5
[ 208.840576] BTRFS error (device dm-1): open_ctree failed
Any idea if this can be fixed?
Cheers
Lee
next reply other threads:[~2019-05-16 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 10:36 Lee Fleming [this message]
2019-05-16 21:39 ` Unbootable root btrfs Chris Murphy
[not found] ` <CAKS=YrMB6SNbCnJsU=rD5gC6cR5yEnSzPDax5eP-VQ-UpzHvAg@mail.gmail.com>
2019-05-18 4:06 ` Chris Murphy
2019-05-18 4:39 ` Robert White
2019-05-18 19:28 ` Chris Murphy
2019-05-18 19:43 ` Lee Fleming
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='CAKS=YrP=z2+rP5AtFKkf7epi+Dr2Arfsaq3pZ9cR3iKif3gV5g@mail.gmail.com' \
--to=leeflemingster@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;
as well as URLs for NNTP newsgroup(s).