gjournal: what is it good for?

[David N]

On 21 April 2010 11:18, Andrew Reilly <areilly at bigpond.net.au> wrote:
> 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
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>

Gjournal on my systems are pretty quick on startup after a power outtage.

What kind of disks are you using? Or what hardware are you using?

Might be the disks are ignoring the BIO_FLUSH.

Regards
David N