Urgent help needed. So, here’s the situation:
- There’s a corrupted useless file that bricks my filesystem if it’s read or deleted. It’s displayed in journal & dmesg logs and pops up as the onlybtrfs check error as no inode ref, pointing to said completely worthless and much hateworthy browser cache file.
- The file is present on multiple snapshots I believe.
- Various non-nuclear options like
btrfs scrub, btrfs rescue zero-log, btrfs rescue super-recover and btrfs rescue clear-ino-cache didn’t help, I haven’t ran btrfs balance nor btrfs rescue chunk-recover just yet though as they’re the lengthy options.
- I have a filesystem image saved on my pendrive with 128GB (80 left) capacity in case it could help with anything.
- memtest returned pass, my laptop is of a newer model, and the drive is an NVMe SSD, SAMSUNG MZLQ512HBLU-00B00
- I don’t exactly have an option to easily backup my data, as I have no external drives I could connect to, and “just reinstalling” is absolutely out of the question.
I will post more information in replies as I manage to gather some.
btrfs-check output:
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p3
UUID: a7200269-3189-4a22-b302-1cfbae4cbf03
[1/8] checking log skipped (none written)
[2/8] checking root items
[3/8] checking extents
[4/8] checking free space tree
[5/8] checking fs roots
unresolved ref dir 9830117 index 6830983 namelen 40 name 031859150890D52DC96C178F5CB33600F346C4B2 filetype 1 errors 4, no inode ref
unresolved ref dir 9830117 index 6830983 namelen 40 name 031859150890D52DC96C178F5CB33600F346C4B2 filetype 1 errors 4, no inode ref
unresolved ref dir 9830117 index 6830983 namelen 40 name 031859150890D52DC96C178F5CB33600F346C4B2 filetype 1 errors 4, no inode ref
ERROR: errors found in fs roots
found 232727597056 bytes used, error(s) found
total csum bytes: 198569216
total tree bytes: 5820399616
total fs tree bytes: 5144788992
total extent tree bytes: 381665280
btree space waste bytes: 1154625488
file data blocks allocated: 22987009212416
referenced 562857721856
Another note I forgot: I have two block devices. It’s due and a janky history of dual booting Win11, then repurposing the former Win11 partition as an ext4 storage and finally just formatting with Btrfs and adding its space as an extra block device to my main filesystem. Here’s the btrfs filesystem usage output:
Overall:
Device size: 459.86GiB
Device allocated: 273.42GiB
Device unallocated: 186.44GiB
Device missing: 0.00B
Device slack: 4.00KiB
Used: 222.29GiB
Free (estimated): 230.94GiB (min: 137.72GiB)
Free (statfs, df): 230.94GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:255.95GiB, Used:211.45GiB (82.61%)
/dev/nvme0n1p3 173.95GiB
/dev/nvme0n1p6 82.00GiB
Metadata,DUP: Size:8.71GiB, Used:5.42GiB (62.26%)
/dev/nvme0n1p3 11.41GiB
/dev/nvme0n1p6 6.00GiB
System,DUP: Size:32.00MiB, Used:48.00KiB (0.15%)
/dev/nvme0n1p6 64.00MiB
Unallocated:
/dev/nvme0n1p3 89.06GiB
/dev/nvme0n1p6 97.38GiB
Finally below are also some not-screenshots of my journal shortly after the Btrfs corruption error occurring. I apologize for the ugly blurry screen photos, I didn’t have the ability to easily and quickly copypaste journal contents at the time, and rebooting would void some of it.
