On Sun, May 24, 2020 at 3:31 PM Marc MERLIN <marc@xxxxxxxxxxx> wrote: > > My data is fine, it's double backed up and the filesystem is still mountable without issues. > But I had an error that broke btrfs send, and after fixing it with repair, I'm stuck with thses 'csum missing' I'm not following the sequence of events. The send|receive failed? Did you try deleting the failed received snapshot? > which I was able to fix with the repair below, but now I'm stuck with the 'some csum missing'. > Checking filesystem on /dev/mapper/cr > UUID: 4cb82363-e833-444e-b23e-1597a14a8aab > [1/7] checking root items > [2/7] checking extents > data backref 2694234112 root 356 owner 14058737 offset 0 num_refs 0 not found in extent tree > incorrect local backref count on 2694234112 root 356 owner 14058737 offset 0 found 1 wanted 0 back 0x55e7383a3a00 > incorrect local backref count on 2694234112 root 2147484004 owner 14058737 offset 0 found 0 wanted 1 back 0x55e733d1c2b0 > backref disk bytenr does not match extent record, bytenr=2694234112, ref bytenr=0 > backpointer mismatch on [2694234112 8192] > ERROR: errors found in extent allocation tree or chunk allocation > [3/7] checking free space cache > [4/7] checking fs roots > root 356 inode 33037179 errors 100, file extent discount > Found file extent holes: > start: 0, len: 8192 > root 203332 inode 33037179 errors 100, file extent discount > Found file extent holes: > start: 0, len: 8192 Is no-holes enabled on either file system? -- Chris Murphy
