On gjournal vs unexpected shutdown (-->fsck)

Andrew Reilly areilly at bigpond.net.au
Thu Dec 17 03:07:08 UTC 2009

On Thu, Dec 17, 2009 at 12:25:00PM +1100, David N wrote:
> 2009/12/16 Andrew Reilly <areilly at bigpond.net.au>:
> > 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?


> 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



More information about the freebsd-fs mailing list