On Wed, 2007-10-24 at 16:04 -0400, Bill Davidsen wrote: > I think what you really want is to notice how long the drive and driver > took to recover or fail, and take action based on that. In general "kick > the drive" is not optimal for a few bad spots, even if the drive > recovery sucks. The problem is that the driver never comes back and the whole array hangs, waiting forever. That's why a timeout within the md code is needed to recover from these type of drivers. Alberto - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
