On Thu, Oct 12, 2017 at 6:16 AM, Alexander Shenkin <al@xxxxxxxxxxx> wrote: > On 10/12/2017 2:04 PM, Phil Turmel wrote: >> >> On 10/12/2017 07:01 AM, Wols Lists wrote: >>> >>> On 12/10/17 10:50, Alexander Shenkin wrote: >>>> >>>> Thanks Phil... Googling around, I haven't found a way to change it >>>> either, but then again, I'm not really sure what to search for. >>>> >>>> What about changing my default disk timeout to something less than 120 >>>> secs? Say, 100 secs instead of 180? >> >> >> Nope. The number has to be longer than the actual longest timeout of >> your drive, which we now know is >120. When I first investigated this >> phenomenon years ago, I picked 120 for my timeouts. Other reports >> reached the list with the need for longer, and the recommendation for >> 180 was chosen. >> >> If the driver times out, it resets the SATA connection while the drive >> is still in la-la land. MD gets the error and tries to write the fixed >> sector. The SATA connection is still resetting at that point, and MD >> gets a *write* error, which boots that drive out of the array. > > > Thanks Phil. Lots of questions in my head, but all rather newbie-ish and > don't want to bother folks, so I'll just wait till you experts hash it out > and then will follow recommendations... > > thanks, > allie Not an expert here but on my Gentoo systems all running kernel 4.12.12 I have the hangcheck timer disabled. Using it does not appear to be a hard requirement. - Mark -- 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
