From owner-freebsd-questions@FreeBSD.ORG Thu Sep 24 12:05:21 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB81065670 for ; Thu, 24 Sep 2009 12:05:21 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 5B3FE8FC1E for ; Thu, 24 Sep 2009 12:05:21 +0000 (UTC) Received: from haran.polands.org ([75.87.219.217]) by hrndva-omta04.mail.rr.com with ESMTP id <20090924120520505.OZMG12959@hrndva-omta04.mail.rr.com>; Thu, 24 Sep 2009 12:05:20 +0000 Received: from email.polands.org (ammon.polands.org [172.16.1.7]) by haran.polands.org (8.14.3/8.14.3) with ESMTP id n8OC5E5L038979; Thu, 24 Sep 2009 07:05:14 -0500 (CDT) (envelope-from doug@polands.org) Received: from 209.103.215.99 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Thu, 24 Sep 2009 07:05:15 -0500 Message-ID: <477581fd1fd93eb97e1718180ba2cd05.squirrel@email.polands.org> In-Reply-To: <6201873e0909231907h293bfe30g90cd989f12837d71@mail.gmail.com> References: <6201873e0909231907h293bfe30g90cd989f12837d71@mail.gmail.com> Date: Thu, 24 Sep 2009 07:05:15 -0500 From: "Doug Poland" To: "Adam Vande More" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Doug Poland , questions@freebsd.org Subject: Re: panic: Journal overflow X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2009 12:05:21 -0000 On Wed, September 23, 2009 21:07, Adam Vande More wrote: > On Wed, Sep 23, 2009 at 6:35 PM, Doug Poland wrote: > >> Hello, >> >> I've got a 7.2-RELEASE (i386) box that has recently experienced >> several panics when writing to a gjournaled partition. On this >> particular partition, the journal device is "mixed" in with the data >> provider. In both cases, I was trying to copy a 19GB file from an >> external USB device (da1p16.journal) to the filesystem on a 3Ware >> RAID-10 (da7p0.journal). >> >> This afternoon I saw... >> >> panic: Journal overflow (joffset=xxxxxxx active=yyyyyyyy >> inactive=zzzzzz) >> cpuid = 1 >> Uptime: >> Physical memory: 1011 MB >> Dumping 351MB >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0, apic id = 00 >> fault virtual address = 0xea60 >> fault code = supervisor write, page not present >> instructor pointer = 0x20: 0xc04715b6 >> stack pointer = 0x28: 0xe6ab0320 >> frame pointer = 0x28: 0xe6ab03bc >> code segment = base 0x0, limit 0xfffff, type 0x1b >> DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, 10PL = 0 >> current process = 48 (gjournal da0p7) >> trap number = 12 >> >> Does this mean my journal is not big enough for the amount of >> data I'm trying to push through? > > > No, it's kinda like the journal is a is a buffer and you overflowed > it. You can address this by two methods: > > 1) slow the rate of transfer > 2) make a bigger journal > >> Any suggestions on how to resolve this? >> > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html > > Well, that's what I was afraid of. Looks like a training opportunity to remove and re-implement journaling on an existing partition, after backups, of course. Thanks for your help. -- Regards, Doug