Looks like they're already fixed: [Sat Feb 24 06:04:54 2018] BTRFS info (device sde): read error corrected: ino 181466 off 114257920 (dev /dev/sdi sector 5332484024) Question is why there's bad data. You can use 'btrfs dev stats' to show the errors on all devices. If the errors are fairly distributed, it could be memory related but usually it'll affect both copies, which isn't the case here. So I think probably it's a device stack problem: cable, controller, drive, vibration, something like that. --- 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
