Re: BTRFS Raid5 error during Scrub.

[Robert Krig <robert.krig@render-wahnsinn.de>]

I've upgraded to btrfs-progs v5.2.1
Here is the output from btrfs check -p --readonly /dev/sda


Opening filesystem to check...
Checking filesystem on /dev/sda
UUID: f7573191-664f-4540-a830-71ad654d9301
[1/7] checking root items                      (0:01:17 elapsed,
5138533 items checked)
parent transid verify failed on 48781340082176 wanted 109181 found
109008items checked)
parent transid verify failed on 48781340082176 wanted 109181 found
109008
parent transid verify failed on 48781340082176 wanted 109181 found
109008
Ignoring transid failure
leaf parent key incorrect 48781340082176
bad block 48781340082176
[2/7] checking extents                         (0:03:22 elapsed,
1143429 items checked)
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space cache                (0:05:10 elapsed, 7236
items checked)
parent transid verify failed on 48781340082176 wanted 109181 found
109008ems checked)
Ignoring transid failure
root 15197 inode 81781 errors 1000, some csum missing48 elapsed, 33952
items checked)
[4/7] checking fs roots                        (0:42:53 elapsed, 34145
items checked)
ERROR: errors found in fs roots
found 22975533985792 bytes used, error(s) found
total csum bytes: 16806711120
total tree bytes: 18733842432
total fs tree bytes: 130121728
total extent tree bytes: 466305024
btree space waste bytes: 1100711497
file data blocks allocated: 3891333279744
 referenced 1669470507008



Am Montag, den 30.09.2019, 09:01 +0300 schrieb Nikolay Borisov:
> 
> On 30.09.19 г. 0:38 ч., Robert Krig wrote:
> > Hi guys. First off, I've got backups so no worries there. I'm just
> > trying to understand what's happening and which files are affected.
> > I've got a scrub running and the kernel dmesg buffer spit out the
> > following:
> > 
> > BTRFS warning (device sda): checksum/header error at logical
> > 48781340082176 on dev /dev/sdb, physical 5651115966464: metadata
> > leaf
> > (level 0) in tree 7
> 
> This indicates you have corrupted checksum tree blocks. Concretely
> the
> checksum in the header does not match the data in the block.
> 
> > BTRFS warning (device sda): checksum/header error at logical
> > 48781340082176 on dev /dev/sdb, physical 5651115966464: metadata
> > leaf
> > (level 0) in tree 7
> > BTRFS error (device sda): bdev /dev/sdb errs: wr 0, rd 0, flush 0,
> > corrupt 0, gen 1
> > BTRFS error (device sda): unable to fixup (regular) error at
> > logical
> > 48781340082176 on dev /dev/sdb
> > BTRFS warning (device sda): checksum/header error at logical
> > 48781340082176 on dev /dev/sdc, physical 5651115966464: metadata
> > leaf
> > (level 0) in tree 7
> > BTRFS warning (device sda): checksum/header error at logical
> > 48781340082176 on dev /dev/sdc, physical 5651115966464: metadata
> > leaf
> > (level 0) in tree 7
> > BTRFS error (device sda): bdev /dev/sdc errs: wr 0, rd 0, flush 0,
> > corrupt 0, gen 1
> > BTRFS error (device sda): unable to fixup (regular) error at
> > logical
> > 48781340082176 on dev /dev/sdc
> > 
> > Is there any way I can find out which files are affected so that I
> > can
> > just restore them from a backup? 
> > 
> > I'm running Debian Buster with Kernel 5.2.
> 
> There was a known corruption issue in 5.2 kernel up to v5.2.15.
> However
> it could result in partial writes of transaction data whereas your
> report seems to indicate data has been written corrupted on-disk.
> 
> As a first step run :
> 
> btrfs check repair --readonly
> 
> (this is a read only command so it cannot do further damage) and post
> the log to see what else btrfs check finds.
> 
> > Btrfs-progs v4.20.1
> > 
> > 
> > Let me know if you need any further info.
> > 
> >