From owner-freebsd-fs@freebsd.org Fri Sep 2 18:03:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5AF8BCD1DF for ; Fri, 2 Sep 2016 18:03:36 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from mail.quorumlabs.com (mail.quorum.net [64.74.133.216]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.quorumlabs.com", Issuer "Go Daddy Secure Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D5527FD3 for ; Fri, 2 Sep 2016 18:03:35 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc]) by QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc%14]) with mapi id 14.02.0318.001; Fri, 2 Sep 2016 11:02:25 -0700 From: Shiva Bhanujan To: "freebsd-fs@freebsd.org" Subject: dnode_evict_dbufs leads to panic Thread-Topic: dnode_evict_dbufs leads to panic Thread-Index: AdIFQ1vC9nt9yylZSTu2+SkzNbv8Zg== Date: Fri, 2 Sep 2016 18:02:24 +0000 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC07013044B954@QLEXC01.Quorum.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.7.61] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 18:03:37 -0000 Hello, We're running FreeBSD 10.2-RELEASE-p20, as a VM (HVM) on XenServer 6.5. It= serves as a backend storage system, and exports ZFS via NFS. After runnin= g for a day and a half, we notice the FreeBSD VM getting hung, or has crash= ed. Looking at the following traceback, I have found this issue being reported = multiple times. #1 0xffffffff8093ce62 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:451 #2 0xffffffff8093d245 in vpanic (fmt=3D, ap=3D) at /usr/src/sys/kern/kern_shutdown.c:758 #3 0xffffffff8093d0d3 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:687 #4 0xffffffff80d3f22b in trap_fatal (frame=3D, eva=3D) at /usr/src/sys/amd64/amd64/trap.c:851 #5 0xffffffff80d3f52d in trap_pfault (frame=3D0xfffffe032937f660, usermode=3D) at /usr/src/sys/amd64/amd64/trap.c:67= 4 #6 0xffffffff80d3ebca in trap (frame=3D0xfffffe032937f660) at /usr/src/sys/amd64/amd64/trap.c:440 #7 0xffffffff80d24f42 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff8094550b in _sx_xlock_hard (sx=3D0xfffff800b3e35918, tid=3D18446735282677829632, opts=3D, file=3D0xfffff8012dad5000 "", line=3D49749) at /usr/src/sys/kern/kern_s= x.c:568 #9 0xffffffff8094501d in _sx_xlock (sx=3D0xfffff8012dad5000, opts=3D766332= 928, file=3D, line=3D766332928) at sx.h:152 #10 0xffffffff819ca67d in dnode_evict_dbufs (dn=3D0xfffff8008c4728d0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/dnode_sync.c:416 #11 0xffffffff819c151b in dmu_objset_evict_dbufs (os=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/dmu_objset.c:620 #12 0xffffffff81a49ff1 in zfsvfs_teardown (zfsvfs=3D0xfffff800adb6e000, unmounting=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/zfs_vfsops.c:1915 #13 0xffffffff81a4b965 in zfs_umount (vfsp=3D0xfffff8007035e330, fflag=3D) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/f= s/zfs/zfs_vfsops.c:2009 #14 0xffffffff809d951f in dounmount (mp=3D0xfffff8007035e330, flags=3D52428= 8, td=3D0xfffff8012dad5000) at /usr/src/sys/kern/vfs_mount.c:1316 #15 0xffffffff809d9026 in sys_unmount (td=3D0xfffff8012dad5000, uap=3D0xfffffe032937fb80) at /usr/src/sys/kern/vfs_mount.c:1208 #16 0xffffffff80d3fb47 in amd64_syscall (td=3D0xfffff8012dad5000, traced=3D= 0) at subr_syscall.c:134 However, I haven't been able to find a definite answer as to how this is to= be fixed. Can anybody provide some guidance if this is something that has= a fix in a subsequent FreeBSD release? If there is more information that = is needed, please do let me know? I can send the core file if needed, have= n't attached it here so as not to spam. Please let me know if I should pro= vide it? Regards, Shiva