On 12/24/2011 10:54 AM, Roger Heflin wrote: > On my Seagates I turned down the SCTERC to really low (ie .2 seconds) > and from what I could see it did not make an obvious difference in > the length of the time that the system paused, the pauses appeared to > stay at about 30 seconds...which I guess implies that the actual read > failed timeout was being hit rather than the disk returning an error > in a reasonable time...from the log each time it was forcing a > re-write it appeared to be 8 sections of 8 sector each so 32k of > data, 64 sectors. I seem to remember there is a way to turn down > the disk op timeout...but at least on my system turning it down lower > would mean that the disks might not have enough time to spinup out of > a sleep... On the drives I've checked closely, any SCTERC setting below 6.5 seconds is discarded and treated as zero (no limit). Setting timeouts in the driver stack below the timeout in the drive is counterproductive, as drives won't abandon the error recovery attempt to reply to the controller's next command. So the drive gets kicked out of the array as completely failed (unresponsive) instead of dealing with the localized read error. If I recall my Seagate spec right, the 6.5 second timeout wouldn't count the spin-up time. I haven't tested that, as my application doesn't sleep. Phil -- 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
