From owner-freebsd-current@FreeBSD.ORG Thu Aug 30 12:31:34 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 58B69106564A for ; Thu, 30 Aug 2012 12:31:34 +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 2B8EF8FC08 for ; Thu, 30 Aug 2012 12:31:33 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T73uB-0008Gx-GN for freebsd-current@freebsd.org; Thu, 30 Aug 2012 05:31:27 -0700 Date: Thu, 30 Aug 2012 05:31:27 -0700 (PDT) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1346329887307-5739274.post@n5.nabble.com> In-Reply-To: References: 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: Thu, 30 Aug 2012 12:31:34 -0000 If I were you, I would try regular fsck, as here (9-STABLE) using journal has left me with fs inconsistencies. -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739274.html Sent from the freebsd-current mailing list archive at Nabble.com.