Chris Murphy posted on Wed, 23 Dec 2015 19:38:23 -0700 as excerpted: > There's a worthwhile distinction between stability of raid56 vs all > other profiles, and btrfs multiple device failure behavior. Right now > there's no monitoring or notification of failures to user space. In > fact Btrfs itself doesn't really understand device failures, a device > can spit out many read or write errors and Btrfs keeps trying to read > and write. So there's no equivalent to faultiness like with md/mdadm. > Therefore you'll have to figure out a way to monitor kernel messages, > maybe via a script that parses for btrfs messages and emails any such > messages ever 10m or whatever. Absolutely. Raid56 mode may be stabilizing, but there's still no user- side multi-device filesystem health monitoring application, either for raid56 or in general, for the raid1/10 modes which are in fact reasonably stable and mature on btrfs and have been considered at the level of btrfs itself for quite awhile (several years), now. Thanks for that addendum, Chris. It could be quite helpful to someone just setting up a new installation, particularly on a server where the user and/or admin is unlikely to be directly observing things and thus know when things go wrong due to the observed change in behavior, regardless of formal monitoring or the lack thereof, as would likely be the case on a desktop/workstation. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
