From owner-freebsd-stable@FreeBSD.ORG  Mon Dec 22 14:09:58 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-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 E3059C10
 for <freebsd-stable@freebsd.org>; Mon, 22 Dec 2014 14:09:58 +0000 (UTC)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com
 [IPv6:2a00:1450:4010:c03::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6768464607
 for <freebsd-stable@freebsd.org>; Mon, 22 Dec 2014 14:09:58 +0000 (UTC)
Received: by mail-la0-f50.google.com with SMTP id pn19so4048367lab.37
 for <freebsd-stable@freebsd.org>; Mon, 22 Dec 2014 06:09:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=nEKgOl7fhNhTniPNIQSDtnqzjgfGBWuDGLOg6sgdv+w=;
 b=p8FUmfXy2DvbVNtYCKNM0Dfpwv1AptqwKke+lkEZEBFDtuZo05eHcgKtJub5tjyAAB
 eW2LKh2gBru69wI2vpwW6pKEraYipwZQFDn7lTy4FrFOodbdA423yRlze8BSJsp+lF51
 P1NahF88S8G33SHGLj8/Gkl0K7aQiNtyPY8T1ycfAKJU1B8KjdHQseNc2LnMEiNK2R9i
 9We5D0DuEC8wC5BbcSm0slUjBQip9MP1a16YbT+bTgPqK6e4hozMRm0DAhgv3Ejtdf/C
 ovOeJNj5q2ymnn+mMLDJw/N24KGZSY1Q4SvTY9w757m9Cn6N3bMdUGfuX8EOu4FnehGz
 2VTg==
MIME-Version: 1.0
X-Received: by 10.112.35.134 with SMTP id h6mr22629553lbj.67.1419257396511;
 Mon, 22 Dec 2014 06:09:56 -0800 (PST)
Received: by 10.114.109.104 with HTTP; Mon, 22 Dec 2014 06:09:56 -0800 (PST)
Date: Mon, 22 Dec 2014 14:09:56 +0000
Message-ID: <CAL6RA3rUu-PSE9TxK6v9eYpEdfjLJ=5qG+bLdb=VEzkzUY9ZAA@mail.gmail.com>
Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command
 timeout
From: Peter HEINER <p.heiner@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 14:09:59 -0000

> So I now think the whole problem centers around the Samsung 850 PRO
> 512GB SSDs. Too bad I do not have the budget to just buy two Intel (or
> other) SSDs of similar size and see if the timeouts disappear..
>
> I wonder if this is a firmware issue with the drive or just some
> misguided fancy energy saving feature of this particular drive
> model causing the whole trouble.

I don't think it's the SSDs, as I'm seeing the exact same behaviour
using 4 2TB WD Reds in a raidz1 with 10.1-RELEASE on a HP N40L as well.
Whenever I do heavy reads like a scrub or send, there are CAM timeouts
and  eventually the drives detach. I had to downgrade to 10.0-RELEASE,
which seems to work fine so far. The box ran Ubuntu until recently,
without issues.
I am happy to troubleshoot further, should anyone want to pick this up.
I'm relatively new to FreeBSD, so any guidance on next steps to take is
welcome.

p