From owner-freebsd-fs@FreeBSD.ORG  Wed Apr 21 01:18:38 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 218D1106564A;
	Wed, 21 Apr 2010 01:18:38 +0000 (UTC)
	(envelope-from areilly@bigpond.net.au)
Received: from nskntmtas02p.mx.bigpond.com (nskntmtas02p.mx.bigpond.com
	[61.9.168.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 757908FC2D;
	Wed, 21 Apr 2010 01:18:37 +0000 (UTC)
Received: from nskntotgx03p.mx.bigpond.com ([124.188.161.100])
	by nskntmtas02p.mx.bigpond.com
	(InterMail vM.7.05.02.08 201-2174-114-118-20080528) with ESMTP id
	<20100421011835.MDWG4632.nskntmtas02p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com>;
	Wed, 21 Apr 2010 01:18:35 +0000
Received: from duncan.reilly.home ([124.188.161.100])
	by nskntotgx03p.mx.bigpond.com with ESMTP id
	<20100421011834.KXOF1978.nskntotgx03p.mx.bigpond.com@duncan.reilly.home>;
	Wed, 21 Apr 2010 01:18:34 +0000
Date: Wed, 21 Apr 2010 11:18:34 +1000
From: Andrew Reilly <areilly@bigpond.net.au>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Message-ID: <20100421011834.GA24928@duncan.reilly.home>
References: <20100418235428.GC4620@duncan.reilly.home>
	<20100420234447.GB1737@garage.freebsd.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100420234447.GB1737@garage.freebsd.pl>
User-Agent: Mutt/1.4.2.3i
X-Authentication-Info: Submitted using SMTP AUTH LOGIN at
	nskntotgx03p.mx.bigpond.com from [124.188.161.100] using ID
	areilly@bigpond.net.au at Wed, 21 Apr 2010 01:18:34 +0000
X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID
	str=0001.0A150205.4BCE526B.005F,ss=1,fgs=0
X-SIH-MSG-ID: qB8wEdz8TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rEJvdRsM6kxDxNJhqENGAoaa/hTY3Rs9mK
Cc: freebsd-fs@freebsd.org
Subject: Re: gjournal: what is it good for?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2010 01:18:38 -0000

Hi Pawel,

Thanks for pointing this out!

On 21/04/2010, at 09:44, Pawel Jakub Dawidek wrote:
> You can still run full fsck on
> gjournaled file system, of course, but in regular use, 'fsck_ffs -p'
> should perform fast fsck.

I think that's the problem: I had assumed that the journal
replay obviated the need for fsck at all, so when mounting was
refused I went straight to "fsck -y", which does a full-scan and
takes just as long as it used to.  Since sending that message
I've been prompted to check the source and now know (!) that I
still need to  run fsck -p.  I just haven't had any crashes in
the mean-time, to give me an opportunity to try that out.

If you have any clues about the journal full with dump -L issue,
that'd be greatly appreciated.  I'm fairly sure I could generate
a crash if I put the "L" back into my backup scripts...

Cheers,

Andrew