From owner-freebsd-stable@FreeBSD.ORG  Wed Feb 19 18:58:41 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 2C1AF422
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 18:58:41 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 023901773
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 18:58:41 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id EA4D6B918;
 Wed, 19 Feb 2014 13:58:39 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-stable@freebsd.org
Subject: Re: FreeBSD FFS SU+J is not stable
Date: Wed, 19 Feb 2014 13:54:37 -0500
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; )
References: <CAO+PfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com>
 <alpine.BSF.2.00.1402190950420.58832@wonkity.com>
In-Reply-To: <alpine.BSF.2.00.1402190950420.58832@wonkity.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201402191354.37749.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Wed, 19 Feb 2014 13:58:40 -0500 (EST)
Cc: Warren Block <wblock@wonkity.com>,
 David Demelier <demelier.david@gmail.com>
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 18:58:41 -0000

On Wednesday, February 19, 2014 11:53:13 am Warren Block wrote:
> 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.

I still have SUJ enabled on my laptop, but I routinely get segfaults in
fsck when rebooting after a panic.  Also, I now always run a full fsck
after the journal fsck (which does sort of defeat the point of SUJ) and
it generally finds missing blocks that are free but marked in use.

I've reported details about the fsck segfaults in the past to no avail. :(

-- 
John Baldwin