Here's a bit more information on these timeouts. I noticed a mention of changing the command queue depth in a recent lkml post and decided to give that a whirl. This problem seems to be related to the depth of the queue. When I set the value for /sys/block/sdb/device/queue_depth to 4 the raid1 re-sync completes without incident. When set to 5 it eventually gives the timeout error message (although at well past 50% of the re-sync). The problem was originally observed with the default setting (31). -- Mike Accetta ECI Telecom Ltd. Data Networking Division (previously Laurel Networks) - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
