Date: Sun, 3 Feb 2008 15:58:25 -0500 From: Gary Palmer <gpalmer@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: gjournal panic 7.0-RC1 Message-ID: <20080203205825.GA62536@in-addr.com> In-Reply-To: <fo58j1$7hq$1@ger.gmane.org> References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> <fo58j1$7hq$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 03, 2008 at 09:35:44PM +0100, Ivan Voras wrote: > Chris wrote: > > >Came back to see box had rebooted itself from a journal related panic. > > > >panic: Journal overflow (joffset=499054080000 active=499691355136 > >inactive=4990$ > >cpuid = 0 > > AFAIK this means that the journal is too small for your machine - try > doubling it until there are no more panics. > > If so, this is the same class of errors as ZFS (some would call it > "tuning errors"), only this time the space reserved for the on-disk > journal is too small, and the fast drives fill it up before data can be > transfered from the journal to the data area. Is there something stopping gjournal from temporarily blocking writes to the journal to allow it to flush the journaled data to the provider? Thanks, Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080203205825.GA62536>