Already we know that Btrfs tries to write indefinitely to missing
devices.
(sorry for the late reply, now back from vacation).
The below and its related patch will take care of it, if when
critical IO fails it can bring the device to an offline / failed
state, so that it prevents further IOs to it.
[PATCH 07/15] btrfs: introduce device dynamic state transition to
offline or failed
Further this could provide btrfs sysfs user interface so that
externally device error monitoring scripts can bring the device
offline / failed. (we need to settle the sysfs framework and
patchset to add that sysfs interface).
If it reappears, what gets written? Will that device be
consistent?
Yep that part of the error handling isn't present. The workaround
for it is to use the remount. (sorry if certain setup considers
remount as not suitable). However this kind of the user involved
recovery option is safe from the intermittently failing devices,
which may lead to a messy situation as you mentioned.
Thanks, Anand
--
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
