On Thu, Nov 26, 2015, at 09:30 PM, Duncan wrote: > What generally happens now, however, is that the btrfs will note failures > attempting to write the device and start queuing up writes. If the > device reappears fast enough, btrfs will flush the queue and be back to > normal. Otherwise, you pretty much need to reboot and mount degraded, > then add a device and rebalance. (btrfs device delete missing broke some > versions ago and just got fixed by the latest btrfs-progs-4.3.1, IIRC.) > > As for alerts, you'd see the pile of accumulating write errors in the > kernel log. Presumably you can write up a script that can alert on that > and mail you the log or whatever, but I don't believe there's anything > official or close to it, yet. Great info, thanks. Just trying to write a file, sync and read it sounds like the easiest test for now, especially since I don't know what the write fail log entries will look like. And setting up SMART notifications. - Ian -- 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
