From owner-freebsd-fs@FreeBSD.ORG Wed Dec 9 01:20:25 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 594AA1065695 for ; Wed, 9 Dec 2009 01:20:25 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwqsrv01p.mx.bigpond.com (nschwqsrv01p.mx.bigpond.com [61.9.189.231]) by mx1.freebsd.org (Postfix) with ESMTP id D7A118FC08 for ; Wed, 9 Dec 2009 01:20:24 +0000 (UTC) Received: from nschwotgx03p.mx.bigpond.com ([124.188.161.100]) by nschwmtas03p.mx.bigpond.com with ESMTP id <20091208224710.BZKY4789.nschwmtas03p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com> for ; Tue, 8 Dec 2009 22:47:10 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20091208224710.XEVW7394.nschwotgx03p.mx.bigpond.com@duncan.reilly.home> for ; Tue, 8 Dec 2009 22:47:10 +0000 Date: Wed, 9 Dec 2009 09:47:10 +1100 From: Andrew Reilly To: freebsd-fs@freebsd.org Message-ID: <20091208224710.GA97620@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nschwotgx03p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Tue, 8 Dec 2009 22:47:10 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150201.4B1ED76E.0089,ss=1,fgs=0 X-SIH-MSG-ID: rRwzEtP7TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rHNvZRtdu1xC5EJhiHNGUnaa3kTY3RstCK Subject: 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, 09 Dec 2009 01:20:25 -0000 Hi there, 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? (Running -current as of last weekend, if that matters.) Cheers, -- Andrew