Am Sat, 2 Apr 2016 09:30:38 +0800 schrieb Anand Jain <anand.j...@oracle.com>:
> Auto replace: > Replace happens automatically, that is when there is any write > failed or flush failed, the device will be marked as failed, which > will stop any further IO attempt to that device. And in the next > commit cycle the auto replace will pick the spare device to > replace the failed device. And so the btrfs volume is back to a > healthy state. Does this also implement "copy-back" - thus, it returns the hot-spare device to global hot-spares when the failed device has been replaced? Traditionally, the wording "hot spare" implies that the storage system runs a copy-back operation when the failing device has been replaced. The "hot spare" device then returns to its original "hot spare" function: sitting and waiting to jump in place... This also helps to keep your drives order in your storage enclosure. Without copy-back, the association between member drive and storage enclosure would fluctuate over time and you'd have to constantly update documentation. Add many identical systems, and you have a lot of different system configurations over time with individual documentation. This becomes confusing at best, and turns out dangerously probably (when pulling the wrong drive due to confusion). Otherwise, I find "hot spare" misleading and it should be renamed. -- Regards, Kai Replies to list-only preferred. -- 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
