On Mon, Jun 27, 2016 at 4:55 PM, Chris Murphy <li...@colorremedies.com> wrote:
>> BTRFS info (device sdb1): dev_replace from /dev/sda1 (devid 1) to /dev/sdd1 >> started >> scrub_handle_errored_block: 166 callbacks suppressed >> BTRFS warning (device sdb1): checksum error at logical 93445255168 on dev >> /dev/sda1, sector 77669048, root 5, inode 3434831, offset 479232, length >> 4096, links 1 (path: user/.local/share/zeitgeist/activity.sqlite-wal) >> btrfs_dev_stat_print_on_error: 166 callbacks suppressed >> BTRFS error (device sdb1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt >> 14221, gen 24 >> scrub_handle_errored_block: 166 callbacks suppressed >> BTRFS error (device sdb1): unable to fixup (regular) error at logical >> 93445255168 on dev /dev/sda1 > > Shoot. You have a lot of these. It looks suspiciously like you're > hitting a case list regulars are only just starting to understand Forget this part completely. It doesn't affect raid1. I just re-read that your setup is not raid1, I don't know why I thought it was raid5. The likely issue here is that you've got legit corruptions on sda (mix of slow and flat out bad sectors), as well as a failing drive. This is also safe to issue: smartctl -l scterc /dev/sda smartctl -l scterc /dev/sdb cat /sys/block/sda/device/timeout cat /sys/block/sdb/device/timeout -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
