From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 16:35:44 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E718106564A for ; Sat, 6 Jun 2009 16:35:44 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 578E08FC0C for ; Sat, 6 Jun 2009 16:35:44 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1MCyru-00019V-Md; Sat, 06 Jun 2009 19:35:42 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Henri Hennebert In-reply-to: <4A2A910A.5060900@restart.be> References: <4A2A910A.5060900@restart.be> Comments: In-reply-to Henri Hennebert message dated "Sat, 06 Jun 2009 17:53:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Jun 2009 19:35:42 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: Stable from May 31 - zfs list locked X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 16:35:45 -0000 > Hello, > > I encounter this problem for the second time. The system is working > perfectly well but suddenly the command `zfs list' don't work and can't > be killed. > > Here is a procstat of the culprit: > > [root@morzine ~]# procstat -k 91766 > PID TID COMM TDNAME KSTACK > > 91766 100490 zfs - mi_switch sleepq_switch > sleepq_wait _cv_wait zio_wait dbuf_read dmu_buf_hold zap_lockdir > zap_lookup_norm zap_lookup dsl_prop_get_dd dsl_dataset_get_ref > dsl_dataset_hold dmu_objset_open zfs_ioc_objset_stats zfsdev_ioctl > devfs_ioctl_f kern_ioctl > > same thing happen if I try to run `zpool list' un another terminal. > > Henri same here, but with a twist: it used to happen on a 7.1, then after an unpgrade, sometime in April, to 7.2-PRERELEASE, things were ok till today! I was about to blame a resent upgrade of the PERC firmware(a very long shot :-), but now I don't know if upgradeing to 7.2-stable will help. This is a production host, with 12TB serving many nfs clients. danny