From owner-freebsd-fs@FreeBSD.ORG Fri Nov 1 17:45:43 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 038B230F; Fri, 1 Nov 2013 17:45:43 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C43092CF4; Fri, 1 Nov 2013 17:45:42 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id rA1HjbL9057122; Fri, 1 Nov 2013 10:45:38 -0700 (PDT) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201311011745.rA1HjbL9057122@chez.mckusick.com> To: Shawn Wallbridge Subject: Re: FFS Softdep Kernel Panic In-reply-to: Date: Fri, 01 Nov 2013 10:45:37 -0700 From: Kirk McKusick Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 17:45:43 -0000 > From: Shawn Wallbridge > To: Kirk McKusick , > "freebsd-fs@freebsd.org" > > CC: John Baldwin > Subject: Re: FFS Softdep Kernel Panic > Date: Fri, 1 Nov 2013 17:30:57 +0000 > > On 11/1/13 9:56 AM, "Kirk McKusick" wrote: > >>I have taken a look at your bug report and have a couple of questions >>about your system: >> >>Your kernel was built at the end of September. Has this problem >>persisted since that kernel was build, or has it showed up more recently? >> >>Are you running with journaled soft updates or just regular soft >>updates? You can use the mount command with no arguments to find out. >> >> Kirk McKusick >> > > Thank you. > > This machine was originally built using 9.1-RELEASE, which had the problem > as well, so I updated to 9.2-RELEASE to try to resolve the issue. > > I am running both, > > /dev/da0p1 on /sam (ufs, NFS exported, local, journaled soft-updates) > > I am building a kernel with invariants right now. > > shawn The problem that you are seeing is probably not related to the journaling, but it would be helpful if you could try running with just soft updates to see if the problem goes away. To do this you need to unmount /sam (or at least downgrade it to read-only), then run: tunefs -j disable /sam Then remount /sam (or reenable writing) and use `mount' to verify that it worked. Also `rm /sam/.sujournal'. Run with that configuration and see if the problem persists. Kirk McKusick