When one device fails it has to be closed and marked as failed. Further it needs sysfs (or some) interface to provide complete information about the device and the volume status to the user land from the kernel. Next when the disappeared device reappears we need to resilver/insync depending on the RAID profile which should be handled per RAID profile specific.
The efforts here are to fix above three missing items. To begin with this patch brings a Write/Flush failed device to a failed state. Next about bringing the device back to the alloc list and verifying its consistency and kicking off the re-silvering part that still WIP, & feedback helps. For RAID1 a convert of single raid profile back to all raid1 will help. For RAID56 I am backing on Luibo's recent RAID56 write hole work I am yet to look deeper on that. Next for RAID1 there can be split brain scenario where each of the devices were mounted independently, so to fix this I planning to set an (new) incompatible flag if any of the device is written without the other. Now when they are brought together then incompatible flag should be their on only one of the device, however if incompatible flag is on both the devices then its a split brain scenario where user intervention will be required. On the sysfs part there are patches in the ML which was sent before, I shall be reviving them as well. Thanks, Anand Anand Jain (2): btrfs: introduce device dynamic state transition to failed btrfs: check device for critical errors and mark failed fs/btrfs/ctree.h | 2 + fs/btrfs/disk-io.c | 78 ++++++++++++++++++++++++++++++++++++++- fs/btrfs/volumes.c | 105 +++++++++++++++++++++++++++++++++++++++++++++++++++++ fs/btrfs/volumes.h | 19 +++++++++- 4 files changed, 202 insertions(+), 2 deletions(-) -- 2.7.0 -- 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
