gjournaled UFS2 filesystem is gone after power outage

[Andrei Kolu]

On Thursday 26 October 2006 10:34 pm, Pawel Jakub Dawidek wrote:
> On Thu, Oct 26, 2006 at 07:44:44PM +0200, Fluffles wrote:
> > Andrei Kolu wrote:
> > > I got power outage- UPS couldn't handle it this time- have to replace
> > > battery and now I can't read my filesystem that I made for testing
> > > purposes:
> > >
> > > # mount /dev/ad0s4.journal /mnt/ad0s4/
> > > mount: /dev/ad0s4.journal: Operation not permitted
> > > # fsck /dev/ad0s4
> > > fsck: Could not determine filesystem type
> >
> > Well you should use:
> >
> > fsck -t ufs /dev/ad0s4
> > and after that mount it.
> >
> > Right now you should be able to mount the volume with mount -f
> > /dev/ad0s4 <mountpoint>, but that is not recommended.
> >
> > But i were told fsck was not necessary when using gjournal. *shrug*
>
> 'fsck_ffs -p /dev/ad0s4.journal' is needed, but it only handles orphaned
> files, which takes seconds, not hours.

Can I enable background check or at least automatic one? I always forgot to 
add .journal extension.