From owner-freebsd-fs@FreeBSD.ORG Wed Dec 16 00:02:03 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AACB106566C for ; Wed, 16 Dec 2009 00:02:03 +0000 (UTC) (envelope-from hywel@hmallett.co.uk) Received: from lisbon.directrouter.com (lisbon.directrouter.com [72.249.30.130]) by mx1.freebsd.org (Postfix) with ESMTP id 7697A8FC0C for ; Wed, 16 Dec 2009 00:02:03 +0000 (UTC) Received: from hmallett.plus.com ([81.174.158.104] helo=[192.168.0.10]) by lisbon.directrouter.com with esmtpa (Exim 4.69) (envelope-from ) id 1NKfHL-0007fA-7s; Tue, 15 Dec 2009 15:49:59 -0600 Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Hywel Mallett In-Reply-To: <20091208224710.GA97620@duncan.reilly.home> Date: Tue, 15 Dec 2009 21:49:56 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <228D9370-4967-4C47-9746-8475DCD4FA27@hmallett.co.uk> References: <20091208224710.GA97620@duncan.reilly.home> To: Andrew Reilly X-Mailer: Apple Mail (2.1077) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - lisbon.directrouter.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - hmallett.co.uk X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-fs@freebsd.org Subject: Re: On gjournal vs unexpected shutdown (-->fsck) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 00:02:03 -0000 On 8 Dec 2009, at 22:47, Andrew Reilly wrote: > Hi there, >=20 > I thought that I'd try a gjournal'd UFS on one of my spare > drives (so: dedicated to the task, formatted from clean, per the > instructions in the gjournal man page.) The filesystem itself > seems to be working swimmingly, although it isn't heavily used. > In the time that I've had it running, though, I've had two power > outages that have resulted in unexpected shutdowns, and I was > surprised to find that the boot process did nothing unexpected: > file system not marked clean: fsck before you can mount. So > both times I fsck'd the drive, and as near as I can tell this > took exactly as long as fsck on a regular UFS system of similar > size. Isn't the journalling operation supposed to confer a > shortcut benefit here? I know that the man page doesn't mention > recovery by journal play-back, but I thought that it didn't need > to: that's the whole point. Is there a step that I'm missing? > Perhaps a gjournal-aware version of fsck that I should run > instead of regular fsck, that will quickly mark the file system > clean? >=20 > (Running -current as of last weekend, if that matters.) >=20 I assume you've run tunefs -J enable on the filesystems on the = journalled provider? Or used newfs with -J if it's a new filesystem? If I remember correctly it's this flag that fsck checks to see whether = fsck is needed or not. You can check whether the flag is set or not by running dumpfs on the = filesystem. Under "flags" it'll say gjournal if the flag is set.=