From: Robert Wyrick <rob@wyrick.org>
To: linux-btrfs@vger.kernel.org
Subject: Next steps in recovery?
Date: Thu, 2 Sep 2021 20:43:54 -0600 [thread overview]
Message-ID: <CAA_aC9-ZAdGC15HY-Q0S-N2M1OukST5BjAk9=WsD+NArCkCFUA@mail.gmail.com> (raw)
I cannot mount my btrfs filesystem.
$ uname -a
Linux bigbox 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11
15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ btrfs version
btrfs-progs v5.4.1
I'm seeing the following from check:
$ btrfs check -p /dev/sda
Opening filesystem to check...
Checking filesystem on /dev/sda
UUID: 75f1f45c-552e-4ae2-a56f-46e44b6647cf
[1/7] checking root items (0:00:59 elapsed,
2649102 items checked)
ERROR: invalid generation for extent 38179182174208, have
140737491486755 expect (0, 4057084]
[2/7] checking extents (0:02:17 elapsed,
1116143 items checked)
ERROR: errors found in extent allocation tree or chunk allocation
cache and super generation don't match, space cache will be invalidated
[3/7] checking free space cache (0:00:00 elapsed)
[4/7] chunresolved ref dir 8348950 index 3 namelen 7 name posters
filetype 2 errors 2, no dir index
unresolved ref dir 8348950 index 3 namelen 7 name poSters filetype 2
errors 5, no dir item, no inode ref
[4/7] checking fs roots (0:00:42 elapsed,
108894 items checked)
ERROR: errors found in fs roots
found 15729059057664 bytes used, error(s) found
total csum bytes: 15313288548
total tree bytes: 18286739456
total fs tree bytes: 1791819776
total extent tree bytes: 229130240
btree space waste bytes: 1018844959
file data blocks allocated: 51587230502912
referenced 15627926712320
I've tried everything I've found on the internet, but haven't
attempted to repair based on the warnings...
What more info do you need to help me diagnose/fix this?
Thanks!
-Rob
next reply other threads:[~2021-09-03 2:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 2:43 Robert Wyrick [this message]
2021-09-03 2:47 ` Next steps in recovery? Robert Wyrick
2021-09-03 6:48 ` Qu Wenruo
2021-09-03 6:53 ` Qu Wenruo
[not found] ` <CAA_aC99-C8xOf7EAvJAMk2ZkYSaN2vyK7YFMw06utQ0T+tsh9A@mail.gmail.com>
2021-09-05 22:03 ` Qu Wenruo
2021-09-06 14:42 ` Robert Wyrick
2021-09-06 23:26 ` Qu Wenruo
2021-09-07 2:36 ` Robert Wyrick
2021-09-07 3:06 ` Anand Jain
2021-09-07 4:36 ` Robert Wyrick
2021-09-07 4:53 ` Qu Wenruo
2021-09-07 17:02 ` Robert Wyrick
2021-09-07 17:17 ` Robert Wyrick
2021-09-07 20:47 ` Robert Wyrick
2021-09-07 23:17 ` Qu Wenruo
2021-09-07 23:20 ` Robert Wyrick
2021-09-07 23:28 ` Qu Wenruo
2021-09-07 23:15 ` Qu Wenruo
2021-09-08 1:59 ` Su Yue
2021-09-08 6:50 ` Robert Wyrick
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='CAA_aC9-ZAdGC15HY-Q0S-N2M1OukST5BjAk9=WsD+NArCkCFUA@mail.gmail.com' \
--to=rob@wyrick.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.