From owner-freebsd-current@FreeBSD.ORG Fri Aug 31 07:42:00 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 A4958106566C for ; Fri, 31 Aug 2012 07:42:00 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7437D8FC08 for ; Fri, 31 Aug 2012 07:41:59 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so4450333pbb.13 for ; Fri, 31 Aug 2012 00:41:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=1TqU3c2ymSW5iVv9kpbngMI/QbsQrFuzmAj12qt4p6o=; b=TTWC7G4Rd6FqvFIykOMxXz3rpZQ1Ofne2sp06OXtKqKxX1Sby4UlNTPQeancuQdqd1 LyGMsli4/+LDoFqPHkGNJbCSxF1dow0Oq+4dmefDxCai6qMq7wETd12UC8A9Tt75wBKc NuoOWpyG8MiAjtS8AFo/T8DrawEzHCNrBFRAKD8nZQ0MMclX6M1GQxuMkb9dIypqEet6 INA7hq3Cyd9QQQj5ltK4fg9ONf12lHbP5IsLmkbm9zPR0vkqBh5s7t6zDUc3Npiuf/gM gRUu/U9RMjTrP3x2Rv5nI0v4QUSVs2bZ/vTHNlt3GFJ1G/anXfbarPDHwY3CNKbx8z33 mnMA== MIME-Version: 1.0 Received: by 10.66.85.70 with SMTP id f6mr14059270paz.7.1346398919264; Fri, 31 Aug 2012 00:41:59 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.66.191.10 with HTTP; Fri, 31 Aug 2012 00:41:59 -0700 (PDT) In-Reply-To: <1346359078818-5739408.post@n5.nabble.com> References: <1346329887307-5739274.post@n5.nabble.com> <1346359078818-5739408.post@n5.nabble.com> Date: Fri, 31 Aug 2012 09:41:59 +0200 X-Google-Sender-Auth: iFIzL58o1gpLEeo5Mj7CpOO2vq8 Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: FreeBSD current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 07:42:00 -0000 2012/8/30 Jakub Lach : > Yes, if I would answer 'yes' to using journal, there would be unexpected > free inodes (?) or something like that in syslog and inconsistencies if f= ull > fsck > would be performed. > That's normally the case, yes, but not here. > Basically if I have answered 'yes' to using journal, fs would always be > marked > 'clean' regardless of state. > I solved it this way, thanks to a tip from Doug White: 1. tunefs -j disable /dev/ada0s1f 2. fsck -y /usr 3 mount /usr ; rm /usr/.sujournal ; umount /usr 4 tunefs -j enable /dev/ada0s1f 5 Step 3 is required because tunefs gets confused when you enable a journal and an (old) journal is already present. Either I should add this somewhere to the Handbook/an article, or fsck(_ufs) should be made more intelligent... Regards, Ren=E9