From owner-freebsd-stable@FreeBSD.ORG Sun Feb 3 16:17:51 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 C0E9C16A417 for ; Sun, 3 Feb 2008 16:17:51 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF7D13C46A for ; Sun, 3 Feb 2008 16:17:51 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so1378548uge.37 for ; Sun, 03 Feb 2008 08:17:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=PE+GVqe0wzKy7cVtw4OX9QbTZrTIkDSC5tcEhk1usyw=; b=AjAxBh1bkXKOMksanCiA02sPPH/G7ixdIgdmnBVbHkybOKhqKsoWNUjTHE5qwRn73MZ3UVNkVKuBrKnb1scvoyQcBbMQk5Rlvlcmyw3RMCsK81dpYPpQkEVDYrG5YMGrMExbbFsQ2NjfmiRvFZNz7iLkv/yNWcqJ2X7Hr1gdAOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nDSW7abEx4Mc5DxZY+XePJG7uhSRU9OzK3fRWXcTQXbdwwJMbuV1N8pS1uZx0XDQIj57lLwtGhmnhC0Fj6lCAqu7pBo/jk0VZcheatJ3ZsrWlFkChFphr7GU7w+WhobcC7CuemafdHY++876sMfhuVi92qiQPolfSPNtW8+7wPI= Received: by 10.67.19.9 with SMTP id w9mr935683ugi.86.1202053900270; Sun, 03 Feb 2008 07:51:40 -0800 (PST) Received: by 10.66.219.18 with HTTP; Sun, 3 Feb 2008 07:51:40 -0800 (PST) Message-ID: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> Date: Sun, 3 Feb 2008 15:51:40 +0000 From: Chris To: "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 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 16:17:51 -0000 I had originally enabled gjournal and seemed to have no problems but I was seeing errors in messages regarding dma write failures and after some research concluded I had setup gjournal incorrectly. I setup the gjournal again properly with soft updates disabled and doing a fresh newfs, mount showed it as enabled and I had the .journal mounted. Started copying files to it from another partition as I wanted to set that up on gjournal also and the copying I felt would be a good stress test to see if the errors stop, the errors were gone and I felt great but as it was about 80 gig of data to copy I went away to do something else for a bit. Came back to see box had rebooted itself from a journal related panic. panic: Journal overflow (joffset=499054080000 active=499691355136 inactive=4990$ cpuid = 0 7.0-RC1 Fair to say this is not as stable as ufs + soft updates then? googling did show other occurances of problem or is there a patch/workaround for the issue? disks are both 500 gig each. Chris