From owner-freebsd-fs@FreeBSD.ORG Wed Aug 27 20:45:50 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F19A1065681; Wed, 27 Aug 2008 20:45:50 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from moe.cs.uoguelph.ca (moe.cs.uoguelph.ca [131.104.94.198]) by mx1.freebsd.org (Postfix) with ESMTP id 4A83D8FC1C; Wed, 27 Aug 2008 20:45:50 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by moe.cs.uoguelph.ca (8.13.1/8.13.1) with ESMTP id m7RKjj3q005786; Wed, 27 Aug 2008 16:45:45 -0400 Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id m7RKvsf28654; Wed, 27 Aug 2008 16:57:55 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 27 Aug 2008 16:57:54 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Weldon S Godfrey 3 In-Reply-To: <20080827161150.G76650@emmett.excelsus.com> Message-ID: References: <20080806101621.H24586@emmett.excelsus.com> <20080814091337.Y94482@emmett.excelsus.com> <20080821153107.W76650@emmett.excelsus.com> <20080821194742.GA19362@eos.sc1.parodius.com> <20080822115932.M76650@emmett.excelsus.com> <20080822174411.GA89610@eos.sc1.parodius.com> <20080827161150.G76650@emmett.excelsus.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.63 on 131.104.94.198 Cc: freebsd-fs@freebsd.org, pjd@freebsd.org Subject: Re: ZFS-NFS kernel panic under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2008 20:45:50 -0000 On Wed, 27 Aug 2008, Weldon S Godfrey 3 wrote: > > Well, I am not sure if it was exactly that bug, since the last time I > paniced, it never dumped to memory. Although this time i paniced, it started > to dump then locked up solid. > > before I paniced I did get an error message at the end of the panic: > > > Stopped at nfsrv_access at 0x190 testb 0x1, 0xa4 (%rax) > Well, I'd guess that is the following source line: if (rdonly || (vp->v_mount->mnt_flag & MNT_RDONLY)) { since "mnt_flag" is way down in the structure and MNT_RDONLY == 0x1. This suggests that v_mount is no longer valid, but I have no idea why that might happen. (This was looking at the -current nfsserver sources, but I don't think they've changed much. Maybe someone who knows ZFS and how it handles the mount structure might have some idea? rick