From owner-freebsd-bugs@freebsd.org Mon Nov 23 10:30:52 2015 Return-Path: Delivered-To: freebsd-bugs@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 858E8A30543 for ; Mon, 23 Nov 2015 10:30:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5827C1EC2 for ; Mon, 23 Nov 2015 10:30:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tANAUqrO064151 for ; Mon, 23 Nov 2015 10:30:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204764] Filesystem deadlock, process in vodead state Date: Mon, 23 Nov 2015 10:30:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rs@bytecamp.net X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2015 10:30:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204764 Bug ID: 204764 Summary: Filesystem deadlock, process in vodead state Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: rs@bytecamp.net Created attachment 163453 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163453&action=edit procstat -kk -a output FreeBSD 10.2-RELEASE-p5 r289218 Deadlock is on an SSD-only mirrored ZFS pool: home ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/mirror0-a ONLINE 0 0 0 gpt/mirror0-b ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gpt/mirror1-a ONLINE 0 0 0 gpt/mirror1-b ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gpt/mirror2-a ONLINE 0 0 0 gpt/mirror2-b ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 gpt/mirror3-a ONLINE 0 0 0 gpt/mirror3-b ONLINE 0 0 0 The deadlocked process is a chksetuid run from periodic. The affected directory is identified. Here is a procstat -kk output: 1816 102485 find - mi_switch+0xe1 sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100 zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb Trying to ls the affected directory ends up in the same: 71376 102400 ls - mi_switch+0xe1 sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100 zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234 vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb However, I'm able to list directory entries via zdb(8). The processes are not killable. The machine is running and non-productive, so I'm able to give any debugging information, just give me some pointers. Attached is the output from procstat -a -kk. -- You are receiving this mail because: You are the assignee for the bug.