From: Josh Rodgers <joshrodgers@tutanota.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Corrupted btrfs?
Date: Tue, 5 Aug 2025 03:02:09 +0200 (GMT+02:00) [thread overview]
Message-ID: <OWrk-6K--F-9@tutanota.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 284 bytes --]
I had an issue with my unraid server where after upgrading to 7.0.1 my cache drive is showing unmountable or no filesystem. I ran a btrfs check and i received the attached output from that check. I wanted to consult the experts before doing any repair.
Thank you,
Josh Rodgers
[-- Attachment #1.2: Type: text/html, Size: 531 bytes --]
[-- Attachment #2: BTRFS Check.txt --]
[-- Type: text/plain, Size: 1764 bytes --]
sudo btrfs check --readonly /dev/nvme0n1p1
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p1
UUID: 0d842f39-ee87-4941-ad71-ee07ec699fb0
[1/8] checking log
[2/8] checking root items
[3/8] checking extents
inline extent refs out of order: key [10259591802880,168,4096]
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32702817 offset 258048) wanted 0 have 1
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32688097 offset 258048) wanted 0 have 1
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32660600 offset 258048) wanted 0 have 1
data extent[10259591802880, 4096] bytenr mimsmatch, extent item bytenr 10259591802880 file item bytenr 0
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32660600 offset 1306624) wanted 1 have 0
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32674309 offset 258048) wanted 0 have 1
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32645602 offset 258048) wanted 0 have 1
data extent[10259591802880, 4096] referencer count mismatch (root 5 owner 32598439 offset 258048) wanted 0 have 1
backpointer mismatch on [10259591802880 4096]
ERROR: errors found in extent allocation tree or chunk allocation
[4/8] checking free space tree
[5/8] checking fs roots
[6/8] checking only csums items (without verifying data)
[7/8] checking root refs
[8/8] checking quota groups skipped (not enabled on this FS)
found 84019183616 bytes used, error(s) found
total csum bytes: 60546480
total tree bytes: 489340928
total fs tree bytes: 323567616
total extent tree bytes: 81166336
btree space waste bytes: 92348555
file data blocks allocated: 1082956144640
referenced 87034966016
next reply other threads:[~2025-08-05 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 1:02 Josh Rodgers [this message]
2025-08-05 2:01 ` Corrupted btrfs? Qu Wenruo
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=OWrk-6K--F-9@tutanota.com \
--to=joshrodgers@tutanota.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