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. > >
