From owner-freebsd-stable@FreeBSD.ORG  Wed Feb 19 20:11:04 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B1A95F4A
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 20:11:04 +0000 (UTC)
Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E2821FAD
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 20:11:03 +0000 (UTC)
Received: from fuzz.geek.sh (unknown [41.13.196.41])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.geek.sh (Postfix) with ESMTPSA id C469E202BC
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 22:04:44 +0200 (SAST)
Message-ID: <53050E59.9070708@phat.za.net>
Date: Wed, 19 Feb 2014 22:04:41 +0200
From: Aragon Gouveia <aragon@phat.za.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Re: FreeBSD FFS SU+J is not stable
References: <CAO+PfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com>
 <53049DA6.4080705@zenker.tk>
In-Reply-To: <53049DA6.4080705@zenker.tk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
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: Wed, 19 Feb 2014 20:11:04 -0000

Hi,

On 02/19/14 14:03, Thomas Zenker wrote:
> setting "sysctl kern.cam.ada.write_cache=0" solved this problem for me.
> Never happened anymore.

FWIW, this has not helped in my case.  Write cache confirmed off with 
camcontrol identify output.  Seagate ST9250410AS.


Regards,
Aragon