From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: unable to mount btrfs after upgrading from 4.16.1 to 4.19.1
Date: Sat, 10 Nov 2018 03:08:01 +0900 [thread overview]
Message-ID: <2442f641ad54ce98361cf40b70e4d18d@virtall.com> (raw)
btrfs sits on md RAID-5:
/dev/md2 /data btrfs noatime,compress-force=zstd,space_cache=v2,noauto 0
0
After upgrading from kernel 4.16.1 to 4.19.1 and a clean restart, the fs
no longer mounts:
# mount /data
mount: wrong fs type, bad option, bad superblock on /dev/md2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
# dmesg
[ 322.877321] BTRFS info (device md2): force zstd compression, level 0
[ 322.877326] BTRFS info (device md2): enabling free space tree
[ 322.877329] BTRFS info (device md2): using free space tree
[ 322.877330] BTRFS info (device md2): has skinny extents
[ 367.832058] BTRFS error (device md2): bad tree block start, want
21120019922944 have 620757027
[ 367.832116] BTRFS error (device md2): failed to read block groups: -5
[ 367.891339] BTRFS error (device md2): open_ctree failed
The error (bad tree block start) in dmesg changes every time as I re-run
"mount /data":
[ 589.425362] BTRFS error (device md2): bad tree block start, want
22008094932992 have 3378573292323635748
[ 589.425423] BTRFS error (device md2): failed to read block groups: -5
[ 589.469979] BTRFS error (device md2): open_ctree failed
[ 680.585908] BTRFS error (device md2): bad tree block start, want
21058406105088 have 18446616720224032488
[ 680.585991] BTRFS error (device md2): failed to read block groups: -5
[ 680.625419] BTRFS error (device md2): open_ctree failed
Any advice how to recover?
Tomasz Chmielewski
https://lxadm.com
next reply other threads:[~2018-11-09 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 18:08 Tomasz Chmielewski [this message]
2018-11-09 18:20 ` unable to mount btrfs after upgrading from 4.16.1 to 4.19.1 Roman Mamedov
2018-11-09 19:15 ` Tomasz Chmielewski
2018-11-09 19:20 ` Tomasz Chmielewski
2018-11-09 20:25 ` Tomasz Chmielewski
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=2442f641ad54ce98361cf40b70e4d18d@virtall.com \
--to=tch@virtall.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).