From owner-freebsd-current@FreeBSD.ORG Fri Aug 31 15:44:39 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BB3C1065676 for ; Fri, 31 Aug 2012 15:44:39 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id EE7C58FC1E for ; Fri, 31 Aug 2012 15:44:38 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T7TOZ-0005Lb-Nc for freebsd-current@freebsd.org; Fri, 31 Aug 2012 08:44:31 -0700 Date: Fri, 31 Aug 2012 08:44:31 -0700 (PDT) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1346427871725-5739669.post@n5.nabble.com> In-Reply-To: References: <1346329887307-5739274.post@n5.nabble.com> <1346359078818-5739408.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: UFS journal error on 10.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2012 15:44:39 -0000 > That's normally the case, yes, but not here. Are you saying that if using journal, inconsistencies in 'clean' fs are expected? Basically I'm saying that apparently here journal does nothing after enabling it. Usually after really hard power dip, I need to manually fsck as all symptoms of unclean fs are apparent. Maybe disabling; fsck; removing journal file; and reenabling it could fix it too? Yes, I'm afraid of it... -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739669.html Sent from the freebsd-current mailing list archive at Nabble.com.