Le mardi 25 août 2015 08:37:46 vous avez écrit : > The errors 200 flags are reasonably common, and I believe > btrfs check --repair handles them well.
Uh, I've started it hours ago, and it has been eating 100% CPU on one of my cores since, without apparently yet finding a single error. It seems that without the --repair flag, btrfs check goes relatively fast, but with this flag (and even on an half-full 500GB SSD), it seems to take forever. I've started it (just for checking) on another machine which FS looked clean in use, and on this other machine it has displayed that it was correcting a huge number of apparently more serious errors. However on this 2nd machine as well, it's taking houuuuurs... > I already stressed the admin rule that no backups means you don't care if > it's lost I'm a white-haired long-beared sysadmin. Nobody ever had more backups than I do ;-))) -- which tends to show that I care about my data. However restoring a complete machine with complex filesystems and snapshots remains a tedious process... -- Swâmi Petaramesh <[email protected]> http://petaramesh.org PGP 9076E32E -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
