Date: Wed, 21 Apr 2010 11:18:34 +1000 From: Andrew Reilly <areilly@bigpond.net.au> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@freebsd.org Subject: Re: gjournal: what is it good for? Message-ID: <20100421011834.GA24928@duncan.reilly.home> In-Reply-To: <20100420234447.GB1737@garage.freebsd.pl> References: <20100418235428.GC4620@duncan.reilly.home> <20100420234447.GB1737@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100421011834.GA24928>