On 07/28/2016 08:53 AM, Anthony Youngman wrote: > I'll just say I don't think the past 16 years is a good guide at all ... > (but I will add I'm doing exactly the same as you - two 3TB desktop > drives in a mirror :-). > > The timeout problem seems to be relatively recent. MOST 1TB or less > drives don't seem to have an issue. It's bigger drives that will bite you. This is not a recent issue. I was first bitten by this in the summer of 2011 when upgrading some Seagate drives from 1T to 2T: http://marc.info/?l=linux-raid&m=133761065622164&w=2 Prior to this, the problem existed in the sense that SCTERC wasn't commonly disabled on powerup for desktop drives. More recent desktop drives don't support it at all. Run "smartctl -l scterc /dev/sdX" on your drives shortly after power-up. You should see a short time setting like this: > SCT Error Recovery Control: > Read: 70 (7.0 seconds) > Write: 70 (7.0 seconds If you see anything else, you will need boot time scripting or udev scripts that will either enable the above, or reset the drive's kernel timeout. If you have this problem and fail to script the corrections, your array will eventually go BOOM, even though your drives aren't actually failed. 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
