Oops.... forgot to copy and past the actual fsck output O:-) # btrfs check /dev/mapper/data-a3 ; echo $? Checking filesystem on /dev/mapper/data-a3 UUID: 326d292d-f97b-43ca-b1e8-c722d3474719 checking extents ref mismatch on [37765120 16384] extent item 0, found 1 Backref 37765120 parent 6403 root 6403 not found in extent tree backpointer mismatch on [37765120 16384] owner ref check failed [37765120 16384] ref mismatch on [51200000 16384] extent item 0, found 1 Backref 51200000 parent 6403 root 6403 not found in extent tree backpointer mismatch on [51200000 16384] owner ref check failed [51200000 16384] ref mismatch on [78135296 16384] extent item 0, found 1 Backref 78135296 parent 6403 root 6403 not found in extent tree backpointer mismatch on [78135296 16384] owner ref check failed [78135296 16384] ref mismatch on [5960381235200 16384] extent item 0, found 1 Backref 5960381235200 parent 6403 root 6403 not found in extent tree backpointer mismatch on [5960381235200 16384] checking free space cache checking fs roots checking csums checking root refs found 7483995824128 bytes used err is 0 total csum bytes: 7296183880 total tree bytes: 10875944960 total fs tree bytes: 2035286016 total extent tree bytes: 1015988224 btree space waste bytes: 920641324 file data blocks allocated: 8267656339456 referenced 8389440876544 0 Also I've found the previous occasion of the apparently same issue: https://www.spinics.net/lists/linux-btrfs/msg45190.html What's the suggested way in reporting bugs? Here on the list? kernel.org bugzilla? It's a bit worrying that even just I myself has reported quite a number of likely bugs here on the ML which never got a reaction from a developer and thus likely still sleep under to hood :-/ Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
