From owner-freebsd-stable@FreeBSD.ORG  Sun Feb  3 20:58:26 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EED1F16A419;
	Sun,  3 Feb 2008 20:58:26 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from noop.in-addr.com (in-addr.broker.freenet6.net
	[IPv6:2001:5c0:8fff:fffe::214d])
	by mx1.freebsd.org (Postfix) with ESMTP id 9E90613C458;
	Sun,  3 Feb 2008 20:58:26 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD))
	id 1JLluz-000Mjd-CY; Sun, 03 Feb 2008 15:58:25 -0500
Date: Sun, 3 Feb 2008 15:58:25 -0500
From: Gary Palmer <gpalmer@freebsd.org>
To: Ivan Voras <ivoras@freebsd.org>
Message-ID: <20080203205825.GA62536@in-addr.com>
References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com>
	<fo58j1$7hq$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fo58j1$7hq$1@ger.gmane.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: gjournal panic 7.0-RC1
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2008 20:58:27 -0000

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