On Sat, 29 Oct 2016, Andreas Klauer wrote:
You'd think timeouts would solve all problems. They probably don't. In some exceedingly rare cases, they might not even matter at all.
My reasoning regarding timeouts, especially for home arrays is the following:
Turning up the timeouts to 180 means your worst case scenario is that your array will have a 180 second long "hiccup" in delivering data.
This can be really bad in an enterprise environment, but in a home environment it's merely in an inconvenience. It happens at very few times, and it stops your drive from being spuriously kicked out when there is a read error, where it being kicked out can lead to lots worse things happening.
So for regular use there is very little downside to set the timeouts to 180 seconds, there are substantial upsides, and I recommend everybody with non-enterprise drives to do that.
I wish the kernel defaults would be changed to 180, because I see these default timeout settings to cause people more problems than they help.
This is of course just one piece of a larger puzzle, but it's one that it's important to get right.
-- Mikael Abrahamsson email: swmike@xxxxxxxxx -- 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
