From owner-freebsd-fs@FreeBSD.ORG Thu Mar 5 15:30:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD7B6106567D for ; Thu, 5 Mar 2009 15:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BB1F88FC1A for ; Thu, 5 Mar 2009 15:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n25FU5nZ022890 for ; Thu, 5 Mar 2009 15:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n25FU5Qh022885; Thu, 5 Mar 2009 15:30:05 GMT (envelope-from gnats) Date: Thu, 5 Mar 2009 15:30:05 GMT Message-Id: <200903051530.n25FU5Qh022885@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Mark Linimon Cc: Subject: Re: kern/132068: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2009 15:30:06 -0000 The following reply was made to PR kern/132068; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/132068: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 Date: Thu, 5 Mar 2009 09:29:11 -0600 ----- Forwarded message from Edward Fisk <7ogcg7g02@sneakemail.com> ----- To: freebsd-bugs@FreeBSD.org From: Edward Fisk <7ogcg7g02@sneakemail.com> Subject: Re: kern/132068: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 I tried with the patch kindly provided by Jaakko. The machine would no longer panic, but would instead deadlock every 1-2 hours when in use. I then did a source upgrade to 8-CURRENT (27022008) with a GENERIC kernel, which had the same result: a deadlock every 1 to 2 hours when in use. The machine is now running a GENERIC kernel with the following options added: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC Unfortunately, I've yet to be able to get it to deadlock, despite the workload on the machine not having changed. ----- End forwarded message -----