On 30/10/16 18:56, TomK wrote: > > We did not do a thorough R/W test to see how the error and bad disk > affected the data stored on the array but did notice pauses and > slowdowns on the CIFS share presented from it with pauses and generally > difficulty in reading data, however no data errors that we could see. > Since then we replaced the 2TB Seagate with a new 2TB WD and everything > is fine even if the array is degraded. But as soon as we put in this > bad disk, it degraded to it's previous behaviour. Yet the array didn't > catch it as a failed disk until the disk was nearly completely > inaccessible. What is this 2TB Seagate? A Barracuda? There's your problem, quite possibly. Sounds like you've got your timeouts correctly matched, so this drive is responding, but taking ages to do so. And that's why it doesn't get kicked, but it knackers system response times - the kernel is correctly configured to wait for the geriatric to respond. Cheers, Wol -- 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
