From owner-freebsd-stable@FreeBSD.ORG  Wed Feb 19 11:16:56 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 8514AAB6
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 11:16:56 +0000 (UTC)
Received: from alogt.com (alogt.com [69.36.191.58])
 (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 57376195D
 for <freebsd-stable@freebsd.org>; Wed, 19 Feb 2014 11:16:56 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com;
 s=default; 
 h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date;
 bh=Y38Tj4XtQmnMf3s4A2zAe3HiIc3fI0eqf4jyBasNnsU=; 
 b=gynnVTTQfNOFJf2YDHn6fRv4O0/5BGS10gO2NM2Swpg4Z9kh3bDz91KxARah1iS3VJfEVLqETd4urSlYBYa9KR0vo7Zl+M/m4CH02oL+wIve27PIF+H/EuweyMSva5UXgGV5XkQbWk4RCMeBJJArT2IKSG3Sia7Lw2dBdsz8H9U=;
Received: from [39.212.216.37] (port=17600 helo=X220.alogt.com)
 by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128)
 (Exim 4.82) (envelope-from <erich@alogt.com>)
 id 1WG594-003fPy-P9; Wed, 19 Feb 2014 04:16:55 -0700
Date: Wed, 19 Feb 2014 19:16:31 +0800
From: Erich Dollansky <erich@alogt.com>
To: David Demelier <demelier.david@gmail.com>
Subject: Re: FreeBSD FFS SU+J is not stable
Message-ID: <20140219191631.49953e37@X220.alogt.com>
In-Reply-To: <CAO+PfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com>
References: <CAO+PfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com>
Organization: ALO Green Technologies
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net
X-AntiAbuse: Original Domain - freebsd.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - alogt.com
X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id:
 erich@alogt.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
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 <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 11:16:56 -0000

Hi,

On Wed, 19 Feb 2014 11:59:49 +0100
David Demelier <demelier.david@gmail.com> 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?

I thought that this got fixed over time. I have had such problems
before too. After turning journaling off, I did not ran into this
trouble anymore. Ok, I also invested in an UPS later.

Erich