From owner-freebsd-stable@FreeBSD.ORG Fri Jan 27 01:32:07 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 7A1B8106566C; Fri, 27 Jan 2012 01:32:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-150-251.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 2AB2A151BF6; Fri, 27 Jan 2012 01:32:07 +0000 (UTC) Message-ID: <4F21FE96.7070805@FreeBSD.org> Date: Thu, 26 Jan 2012 17:32:06 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120119 Thunderbird/9.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ant=F3nio_Trindade?= References: <315A1E95-9064-494F-A3B8-48F1C4951624@gmail.com> In-Reply-To: <315A1E95-9064-494F-A3B8-48F1C4951624@gmail.com> X-Enigmail-Version: 1.3.5 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel: panic: softdep_sync_buf: Unknown type jnewblk 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: Fri, 27 Jan 2012 01:32:07 -0000 On 01/26/2012 16:40, António Trindade wrote: > Cheers. > > I recently updated my system to FreeBSD-9.0 and activated softupdate journaling for a number of file systems (name /home, /var, /usr). > > Since then I have been experiencing kernel panics: > kernel: panic: softdep_sync_buf: Unknown type jnewblk > > Yesterday, Jan 26th, I got 6 (six) automatic reboots due to these kernel panics. > > I have now disabled softupdates journaling in the hope that the panics disappear. > > I am sorry for not providing more information about the panic, but I'll gladly try to gather more info if instructed how to. Make sure that dumpdev is defined in rc.conf. Usually you want to use your swap device. You should also boot into single user mode and do 'fsck -y' to make sure that the file systems are actually clean. There have been problems reported where SU+J doesn't recover fully after a crash, which leads to the kinds of instability you're reporting. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/