Currenly, when failback happens, IO's will be held until failback is completed. After failback happens, IO's will resume on alternate controller. Although this will not induce IO failure, the delay in resuming IO will possibly impact clients that may be accessing the server. If as the path failover is completed, if a failover is again initiated, it delays when IO can start running normally. This is a QoS issue. To prevent quick failover/failback that can be result in IO failure, hysteresis needs to be implemented, such that after redundancy has been restored failback is only executed after the existing backlog of pending IOs have been completed. When failback is scheduled to happen, newly issued IO's will be queued, but failback will be held until all backlog IO's are completed. Any thoughts on this? Thanks, Yanqing -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
