From owner-freebsd-stable@FreeBSD.ORG Fri Feb 20 11:38:49 2015 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCA3498D for ; Fri, 20 Feb 2015 11:38:49 +0000 (UTC) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 823C4C53 for ; Fri, 20 Feb 2015 11:38:49 +0000 (UTC) Received: by iecar1 with SMTP id ar1so7190285iec.0 for ; Fri, 20 Feb 2015 03:38:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=SaI7+gMsFPWlJZOZCwkluXtW0nQUbDOHJgPuofjqL6k=; b=CkNcvo/ZWSIBYxGFj6+D0I7fg+8gY5OIuHyH+A6PM6782oQmePvI8yoT7WwxhbMmLO jY7OnPkl7tX8cqdaNoAcKyM92ARlL2IN7Rm3757U8WxUEMjkKiWAA12HocelKz4qnUqk KFKZaYOZQ4+mqyZt6BKTlx+wB3XGbCQmzXMYDdsH3mLHh0T1gTk9NtrKUmam+VoxL7Yx XlhgTuBgF6ts5Wd+lhXwFC160/s/HzBqnlusvxccPLT25lS0S5ALXYzHDOZqEc5OQgDb YFeUVLAP4++dGR4A78v+gFXb6V2k2EkePJoItWvFlzLjBogiLvDA36pHbHG3cKeDoLQQ ydOA== MIME-Version: 1.0 X-Received: by 10.43.74.201 with SMTP id yx9mr11328714icb.96.1424432328836; Fri, 20 Feb 2015 03:38:48 -0800 (PST) Received: by 10.107.0.8 with HTTP; Fri, 20 Feb 2015 03:38:48 -0800 (PST) In-Reply-To: <1BFD18FF-D3A7-4230-9425-CEDC7DC94181@tao.org.uk> References: <064CF905-DF19-40A7-8CE8-D9FFE17913EE@tao.org.uk> <938BC03E-2C47-4381-9D21-5849E9E6E126@gid.co.uk> <1BFD18FF-D3A7-4230-9425-CEDC7DC94181@tao.org.uk> Date: Fri, 20 Feb 2015 11:38:48 +0000 Message-ID: Subject: Re: ada drives keep timing out! From: Tom Evans To: Dr Josef Karthauser Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2015 11:38:49 -0000 On Fri, Feb 20, 2015 at 11:21 AM, Dr Josef Karthauser wrot= e: > In this case other report no such issues on the same hardware running Lin= ux, so it seems to me to be an internal timeout issue within FreeBSD, or ma= ybe Linux retries more than FreeBSD and so doesn=E2=80=99t experience the i= ssue that we do. It=E2=80=99s clear that FreeBSD is proactively disconnecti= ng the drive when the timeout occurs. So, maybe there=E2=80=99s something t= hat can be done there. Linux has more automatic quirks for troublesome hardware, it may also have a longer default timeout. FreeBSD's WD green drives are green, they spin down frequently if idle. If you then try and use them, they can take considerably longer than the timeout to spin back up and be ready, and the kernel gives up. You can make the WD green drives less green by using a dos tool, wdidle3.exe. Google will tell you more (and show that WD green drives cause people problems on all OS when they use them in RAID). The continual parking/unparking considerably reduces the life of disk. You can tell BSD to wait longer with a higher "kern.cam.ada.default_timeout= ". Cheers Tom