From: Dave T <davestechshop@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: ref mismatch / root not found in extent tree / backpointer mismatch / owner ref check failed
Date: Fri, 3 May 2019 20:22:32 -0400 [thread overview]
Message-ID: <CAGdWbB5-iCfWD3NXuNHU+QVF4RWKptkzjyYwX_HteR1wshVV0Q@mail.gmail.com> (raw)
The filesystem has become very, very slow. smartctl doesn't show any
problems with the HDD. My usual btrfs maintenance (balance, scrub,
defrag) did not show any problems -- but did not resolve the slowness.
So I ran a btrfs check -- the result is pasted below. What causes this
and is there any solution other than recreating the file system? Would
the errors shown below make a btrfs filesystem slow?
Opening filesystem to check...
Checking filesystem on /dev/mapper/bak_luks
UUID: 3ac770bc-e7c4-4792-2d2d-1d3ed19d126b
[1/7] checking root items
[2/7] checking extents
ref mismatch on [374849568768 16384] extent item 0, found 1
tree backref 374849568768 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [374849568768 16384]
owner ref check failed [374849568768 16384]
ref mismatch on [374940549120 16384] extent item 0, found 1
tree backref 374940549120 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [374940549120 16384]
owner ref check failed [374940549120 16384]
ref mismatch on [569319473152 16384] extent item 0, found 1
tree backref 569319473152 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [569319473152 16384]
ref mismatch on [569329385472 16384] extent item 0, found 1
tree backref 569329385472 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [569329385472 16384]
ref mismatch on [569516376064 16384] extent item 0, found 1
tree backref 569516376064 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [569516376064 16384]
ref mismatch on [570749665280 16384] extent item 0, found 1
tree backref 570749665280 parent 6835 root 6835 not found in extent tree
backpointer mismatch on [570749665280 16384]
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 3655790232414 bytes used, error(s) found
total csum bytes: 3534402188
total tree bytes: 46277705728
total fs tree bytes: 34533392384
total extent tree bytes: 7925743616
btree space waste bytes: 8021706864
file data blocks allocated: 30545889550336
referenced 31161532510208
next reply other threads:[~2019-05-04 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 0:22 Dave T [this message]
2019-05-04 19:15 ` ref mismatch / root not found in extent tree / backpointer mismatch / owner ref check failed Chris Murphy
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=CAGdWbB5-iCfWD3NXuNHU+QVF4RWKptkzjyYwX_HteR1wshVV0Q@mail.gmail.com \
--to=davestechshop@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).