From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 20:58:45 2008 Return-Path: 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 76DCF16A498 for ; Sun, 3 Feb 2008 20:58:45 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 4A50613C448 for ; Sun, 3 Feb 2008 20:58:45 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost.egr.msu.edu [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 876672EB9EF; Sun, 3 Feb 2008 15:58:44 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1O777AdvJPSx; Sun, 3 Feb 2008 15:58:44 -0500 (EST) Received: from [10.0.0.211] (c-208-53-102-126.chrlmi.cablespeed.com [208.53.102.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTP id 41ED32EB9EB; Sun, 3 Feb 2008 15:58:44 -0500 (EST) Message-ID: <47A62B00.1060403@egr.msu.edu> Date: Sun, 03 Feb 2008 15:58:40 -0500 From: Adam McDougall User-Agent: Thunderbird 2.0.0.9 (X11/20080203) MIME-Version: 1.0 To: Ivan Voras References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2008 20:58:45 -0000 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. > I did some experimentation with gjournal a few weeks ago to determine how I might partition a new server, as well as how large to make my journals and where. I did find that for the computers I have tested so far, a 1 gig (default size) journal seems to be sufficient, but half of that or less is asking for trouble and I could not find any workarounds to reduce the chances of panic when I was already stuck with a too-small journal I created a while ago. I also found the -s parameter is vague in that it does not say what units it accepts (appears to be bytes) and I *could not* get it to make a journal inside a data partition any bigger than somewhere around 1.7 gigs. Some values of -s seemed to wrap around to a smaller number, while other values gave errors about being too small (when they weren't) or invalid size. The only way I could force a journal size 2G or larger was to make a separate partition for journal. On the server I was setting up, I decided to make my (journaled) data partitions da0s1d,e,f and the journals da0s2d,e,f. I'm just getting this out there to the list because I don't have time to debug it further.