Hey Qu. Some update on the corruption issue on my Fujitsu notebook:
Finally got around running some memtest on it... and few seconds after it started I already got this: https://paste.pics/1ff8b13b94f31082bc7410acfb1c6693 So plenty of bad memory... I'd say it's probably not so unlikely that *this* was the actual reason for btrfs-metadata corruption. It would perfectly fit to the symptom that I saw shortly before the fs was completely destroyed: The spurious csum errors on reads that went away when I read the file again. I'd guess you also found no further issue with the v1 space cache and/or the tree log in the meantime? So it's probably safe to turn them on again? We(aka you + me testing fixes) can still look in the issue that newer btrfsprogs no longer recover anything from the broken fs, while older to. I can keep the image around, so no reason to hurry from your side. Cheers, Chris. -- 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
