On Thu, Jan 12, 2017, 2:55 AM Gregory Petit <gregory@xxxxxxxxxxxxxxxx> wrote: > Here are the details: > > scrub started at Wed Jan 11 18:00:01 2017 and finished after 00:19:23 > total bytes scrubbed: 1.14TiB with 4 errors > error details: csum=4 > corrected errors: 0, uncorrectable errors: 4, unverified errors: 0 > > From dmesg: > Wed Jan 11 18:10:35 2017] BTRFS error (device sda): bdev /dev/sda errs: > wr 0, rd 0, flush 0, corrupt 1, gen 0 > [Wed Jan 11 18:10:35 2017] BTRFS error (device sda): unable to fixup > (regular) error at logical 631657844736 on dev /dev/sda > [Wed Jan 11 18:10:51 2017] BTRFS error (device sda): bdev /dev/sdb errs: > wr 0, rd 0, flush 0, corrupt 1, gen 0 > [Wed Jan 11 18:10:51 2017] BTRFS error (device sda): unable to fixup > (regular) error at logical 632954847232 on dev /dev/sdb > [Wed Jan 11 18:18:57 2017] BTRFS error (device sda): bdev /dev/sdc errs: > wr 0, rd 0, flush 0, corrupt 1, gen 0 > [Wed Jan 11 18:18:57 2017] BTRFS error (device sda): unable to fixup > (regular) error at logical 632954847232 on dev /dev/sdc > [Wed Jan 11 18:19:19 2017] BTRFS error (device sda): bdev /dev/sde errs: > wr 0, rd 0, flush 0, corrupt 1, gen 0 > [Wed Jan 11 18:19:19 2017] BTRFS error (device sda): unable to fixup > (regular) error at logical 631657844736 on dev /dev/sde Look at the logical addresses. Two pair, four total, have errors. Looks like both copies of two blocks of information are corrupt, and that's why fix up doesn't happen. I'm gonna guess this is metadata. But between 'btrfs inspect-internal logical-resolve' or 'dump-tree' with those two block numbers, you should be able to figure out what's affected. Pretty strange for both copies to get munged though, but I'm suspicious of hardware - in particular controller or cable or even RAM, since it affects at least two drives. The chances this is two drives corrupting the same logical block of data is almost zero. > > root@proxmox:~# btrfs check --repair /dev/sda FWIW btrfs check finds all member devices for you regardless of which device you point it to, and checks the whole file system. It's not necessary to run it on each device. 'btrfs check --mode=lowmem' might find the problem but I don't think it can fix anything still. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
