From owner-freebsd-fs@FreeBSD.ORG Thu Dec 17 03:07:08 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 4DD8F1065672 for ; Thu, 17 Dec 2009 03:07:08 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas02p.mx.bigpond.com (nschwmtas02p.mx.bigpond.com [61.9.189.140]) by mx1.freebsd.org (Postfix) with ESMTP id CCAAE8FC0A for ; Thu, 17 Dec 2009 03:07:07 +0000 (UTC) Received: from nschwotgx03p.mx.bigpond.com ([124.188.161.100]) by nschwmtas02p.mx.bigpond.com with ESMTP id <20091217030705.VIGU2264.nschwmtas02p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com>; Thu, 17 Dec 2009 03:07:05 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20091217030705.VNRF5111.nschwotgx03p.mx.bigpond.com@duncan.reilly.home>; Thu, 17 Dec 2009 03:07:05 +0000 Date: Thu, 17 Dec 2009 14:07:05 +1100 From: Andrew Reilly To: David N Message-ID: <20091217030705.GA20153@duncan.reilly.home> References: <20091208224710.GA97620@duncan.reilly.home> <228D9370-4967-4C47-9746-8475DCD4FA27@hmallett.co.uk> <20091215221727.GA8137@duncan.reilly.home> <4d7dd86f0912161725m6278c843xba275038c6a80d59@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d7dd86f0912161725m6278c843xba275038c6a80d59@mail.gmail.com> 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 Thu, 17 Dec 2009 03:07:05 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150202.4B29A059.00E1,ss=1,fgs=0 X-SIH-MSG-ID: rB4xGdb6TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rHK+ZRtdu1xD9LJhqGNGEnaazhTY3RstCK 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: Thu, 17 Dec 2009 03:07:08 -0000 On Thu, Dec 17, 2009 at 12:25:00PM +1100, David N wrote: > 2009/12/16 Andrew Reilly : > > On Tue, Dec 15, 2009 at 09:49:56PM +0000, Hywel Mallett wrote: > >> > >> On 8 Dec 2009, at 22:47, Andrew Reilly wrote: > Do you have soft updates enabled? No. > can you show us a print out of > > tunefs -p /dev/.....journal Sure: (I hadn't seen the -p option before: neat!) duncan [202]$ tunefs -p /dev/ad10.journal tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: gjournal: (-J) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) I have a suspicion that what happened was probably mostly a misunderstanding on my part about how and when the journal playback is initiated. Memory is getting dim at this point: the power outage that brought this issue up was a week or so ago. It seems plausible that since my other (non-journalled) drives were dirty too, I just ran fsck on everything. I expected fsck on the ad10.journal drive to just say "hey this is clean", but it went and did a full, slow, check. But that happens when you run fsck on clean non-journalled drives too, I think, so shouldn't have surprised me. I guess the surprise is that the system claimed that the journalled drive was dirty at all. Maybe it didn't: it's hard to remember now. I'll have to pay more attention the next time there's a power outage (something (not yet identified) is tickling the earth leakage circuit every so often: very annoying.) Cheers, -- Andrew