From owner-freebsd-stable@FreeBSD.ORG Wed Feb 19 16:53:15 2014 Return-Path: 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 D1B24F1A for ; Wed, 19 Feb 2014 16:53:15 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (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 8766F1B78 for ; Wed, 19 Feb 2014 16:53:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.8/8.14.8) with ESMTP id s1JGrE7I060044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Feb 2014 09:53:14 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s1JGrDd9060041; Wed, 19 Feb 2014 09:53:14 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 19 Feb 2014 09:53:13 -0700 (MST) From: Warren Block To: David Demelier Subject: Re: FreeBSD FFS SU+J is not stable In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 19 Feb 2014 09:53:14 -0700 (MST) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 16:53:15 -0000 On Wed, 19 Feb 2014, David Demelier wrote: > 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? Yes, but I would suggest turning off SUJ instead. Soft updates alone have been reliable for me. SUJ, not really.