Date: Thu, 26 Jan 2012 17:54:30 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Doug Barton <dougb@FreeBSD.org> Cc: Ant?nio Trindade <antonio.trindade@gmail.com>, freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel: panic: softdep_sync_buf: Unknown type jnewblk Message-ID: <20120127015430.GA66235@icarus.home.lan> In-Reply-To: <4F21FE96.7070805@FreeBSD.org> References: <315A1E95-9064-494F-A3B8-48F1C4951624@gmail.com> <4F21FE96.7070805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 26, 2012 at 05:32:06PM -0800, Doug Barton wrote: > 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. I'll also point out, though the OP isn't using snapshots, that it's confirmed use of snapshots on SU+J can result in a full filesystem hang. Confirmation is from Kirk McKusick (author of SU and designer of SU+J): http://lists.freebsd.org/pipermail/freebsd-fs/2012-January/013429.html Something really needs to be done about this combination of problems. Since SU+J is the default choice for all UFS filesystems on 9.0-RELEASE, the only solution I can think of is to send a massive announcement to relevant mailing lists, AND put something on the freebsd.org home page about these issues. For the snapshot issue, I believe not using SU+J (and only SU) works around the problem, so possibly that would be the best choice of recommendation at this time. I urge key members of the community and (as always) kernel developers to chime in here with advice. Something needs to be done, users need to be made aware of these problems, and so on. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120127015430.GA66235>