From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: Mdadm server eating drives Date: Fri, 14 Jun 2013 17:24:12 -0400 Message-ID: <51BB89FC.8050503@turmel.org> References: <51B896A2.9090105@websitemanagers.com.au> <51BA7B28.9030808@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Barrett Lewis Cc: "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 06/14/2013 05:18 PM, Barrett Lewis wrote: > I'll definatly do this. When you talk about mismatched timeouts, do > you mean matched between each of the components (as in > /sys/block/sdX/device/timeout) or between that driver timeout and some > device timeout per component? If you mean between components, are my > timeouts matched now, even though I did not raise the 30 seconds on > the two drives with ERC? For each drive, the driver timeout (/sys/block/.../device/timeout) must be longer than the drive's timeout (smartctl -l scterc). Note that scterc is in deciseconds, while the driver uses seconds. Enterprise drives typically power up with 7.0 second timeouts. The few SSDs I've been playing with power up with 4.0 second timeouts. Without ERC, the drives I've played with will perform error recovery for about two full minutes, ignoring the world for the duration. Phil