* Corrupted btrfs?
@ 2025-08-05 1:02 Josh Rodgers
2025-08-05 2:01 ` Qu Wenruo
0 siblings, 1 reply; 2+ messages in thread
From: Josh Rodgers @ 2025-08-05 1:02 UTC (permalink / raw)
To: Linux Btrfs
[-- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Corrupted btrfs?
2025-08-05 1:02 Corrupted btrfs? Josh Rodgers
@ 2025-08-05 2:01 ` Qu Wenruo
0 siblings, 0 replies; 2+ messages in thread
From: Qu Wenruo @ 2025-08-05 2:01 UTC (permalink / raw)
To: Josh Rodgers, Linux Btrfs
在 2025/8/5 10:32, Josh Rodgers 写道:
> 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.
This type of corruption seems to be caused by a regression in ntfs2btrfs
or winbtrfs. That regression itself should have been fixed, the damage
is persistent though.
If that's the case, considering that's the only corruption, it's
possible btrfs check --repair (latest release) can repair it.
Thanks,
Qu
>
> Thank you,
>
> Josh Rodgers
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-05 2:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-05 1:02 Corrupted btrfs? Josh Rodgers
2025-08-05 2:01 ` Qu Wenruo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox