From owner-freebsd-stable@FreeBSD.ORG  Wed Feb 19 12:06:43 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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6729C7D5
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 12:06:43 +0000 (UTC)
Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1E6181E0F
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 12:06:43 +0000 (UTC)
Received: from [195.4.92.142] (helo=mjail2.freenet.de)
 by mout2.freenet.de with esmtpa (ID zenker.ofterdingen@freenet.de) (port 25)
 (Exim 4.80.1 #4) id 1WG5vE-0000AS-Oe
 for freebsd-stable@freebsd.org; Wed, 19 Feb 2014 13:06:40 +0100
Received: from localhost ([::1]:37975 helo=mjail2.freenet.de)
 by mjail2.freenet.de with esmtpa (ID zenker.ofterdingen@freenet.de) (Exim
 4.80.1 #4) id 1WG5vE-0006p4-Ix
 for freebsd-stable@freebsd.org; Wed, 19 Feb 2014 13:06:40 +0100
Received: from mx7.freenet.de ([195.4.92.17]:42340)
 by mjail2.freenet.de with esmtpa (ID zenker.ofterdingen@freenet.de) (Exim
 4.80.1 #4) id 1WG5sV-0005P3-QJ
 for freebsd-stable@freebsd.org; Wed, 19 Feb 2014 13:03:51 +0100
Received: from mail.isepos.de ([46.237.201.241]:61500
 helo=chipotl.isepos.local)
 by mx7.freenet.de with esmtpa (ID zenker.ofterdingen@freenet.de) (port 587)
 (Exim 4.80.1 #4) id 1WG5sV-0004Nc-Hg
 for freebsd-stable@freebsd.org; Wed, 19 Feb 2014 13:03:51 +0100
Message-ID: <53049DA6.4080705@zenker.tk>
Date: Wed, 19 Feb 2014 13:03:50 +0100
From: Thomas Zenker <thz@zenker.tk>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Firefox/24.0 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>
In-Reply-To: <CAO+PfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Originated-At: 46.237.201.241!61500
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 12:06:43 -0000

On 02/19/14 11:59, David Demelier wrote:
> Hello there,
> 
> Running 10.0-RELEASE, it is the second time I have a power failure and
> bad shutdown. It's also the second time I get a fsck failure. This
> time fsck has even segfault'ed.
> 
> I think I will switch to ZFS.
> 
> This is the log of the next boot up : http://imgur.com/rRpREKP
> 
> Is it possible to automatically run fsck manually after this kind of failures?
> 
> Regards,
> 

Hi David,
setting "sysctl kern.cam.ada.write_cache=0" solved this problem for me.
Never happened anymore.

regards, Thomas