From owner-freebsd-current@FreeBSD.ORG Wed Feb 17 23:50:13 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EFA9106570F for ; Wed, 17 Feb 2010 23:50:13 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id DE4AF8FC17 for ; Wed, 17 Feb 2010 23:50:12 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Nhtek-0004E0-9m for freebsd-current@freebsd.org; Thu, 18 Feb 2010 00:50:10 +0100 Received: from k.saper.info ([91.121.151.35]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Feb 2010 00:50:10 +0100 Received: from saper by k.saper.info with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Feb 2010 00:50:10 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Marcin Cieslak Date: Wed, 17 Feb 2010 23:26:36 +0000 (UTC) Organization: http://saper.info Lines: 19 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: k.saper.info X-Face: "MPx|KfVwz7Gg!ayb)rH,hKiCBJXvLY7t+%r1s0Uiw; (%xWn-C-H38.2Oa4JL|4Cx}a"V ~a pL4%i"s20r0%z0yZew?2><1ZfOFF27cPqcAKp?wG+-c&%BgXeJVm[lylYKH?j User-Agent: slrn/0.9.9p1 (FreeBSD) Sender: news X-Mailman-Approved-At: Thu, 18 Feb 2010 00:14:56 +0000 Subject: ZFS DEADLKRES X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 23:50:13 -0000 My r203753 amd64 laptop falls into the deadlock situation every night while running periodic daily script. I am pretty certain this is related to ZFS. I have enabled DEADLKRES in the kernel. I even have a separate dump partition (not used for swap). Indeed, the kernel deadlock detector gets triggered during the periodic run, but I get I/O error when calling doadump() from DDB. Dumping works properly when DDB is invoked with keyboard escape. What's the best way to troubleshoot this deadlock? Should I try to transcribe "alltrace" output? -- << Marcin Cieslak // saper@saper.info >>