On 2016-10-17 16:40, Chris Murphy wrote:
This is exactly why you should be monitoring the disks themselves, not
just BTRFS. I would not advise using blktrace for monitoring in
production though, it technically risks an information leak, and it's
not exactly low impact.
May be better to use /sys/fs/btrfs/<uuid>/devices to find the device
to monitor, and then monitor them with blktrace - maybe there's some
courser granularity available there, I'm not sure. The thing is, as
far as Btrfs alone is concerned, a drive can be "bad" and you're
effectively degraded, while the drive is not missing. Unless it's
physical removed or somehow dead, it'll still be seen but can produce
all kinds of mayhem.
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