Space key logical 1048576 length 4194304 has no corresponding block group

Space key logical 1048576 length 4194304 has no corresponding block group

[Christoph Anton Mitterer]

Hey.


This is on 6.19.10 with progs 6.19.1:
# btrfs check /dev/mapper/data-a-1 ; echo $? ; beep
Opening filesystem to check...
Checking filesystem on /dev/mapper/data-a-1
UUID: ff14e046-d72c-4671-b30a-6ec17c58a0f1
[1/8] checking log skipped (none written)
[2/8] checking root items
[3/8] checking extents
[4/8] checking free space tree
Space key logical 1048576 length 4194304 has no corresponding block group
Space key logical 5242880 length 8388608 has no corresponding block group
[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 15744973131776 bytes used, error(s) found
total csum bytes: 15347594276
total tree bytes: 29036593152
total fs tree bytes: 11069259776
total extent tree bytes: 811499520
btree space waste bytes: 3687899842
file data blocks allocated: 22699997167616
 referenced 18205200039936
1


May have been there earlier (Debian was until yesterday or so on progs
6.18).

Is this something to worry about (the fs is very precious for me,
though I do have backups)?

The fs never crashed so I wonder how these free space tree corruptions
come to happen, any rare bug perhaps?


Should I re-generate the free space tree (which currently is however
not really possible though, due to [0]). So not sure whether I still
can/should use that fs until a fix for that is available?


Thanks,
Chris.


[0] https://lore.kernel.org/linux-btrfs/89188b7b8b5a1f9bb64af37777aec906134ad75c.camel@scientia.org/