From nobody@FreeBSD.org Fri Jun 25 12:30:13 2010 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF34D106566C for ; Fri, 25 Jun 2010 12:30:13 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id BDDA58FC0C for ; Fri, 25 Jun 2010 12:30:13 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5PCUDDb028198 for ; Fri, 25 Jun 2010 12:30:13 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5PCUDqS028197; Fri, 25 Jun 2010 12:30:13 GMT (envelope-from nobody) Message-Id: <201006251230.o5PCUDqS028197@www.freebsd.org> Date: Fri, 25 Jun 2010 12:30:13 GMT From: Marcel Grandemange To: freebsd-gnats-submit@FreeBSD.org Subject: zfs raidz pool commands freeze X-Send-Pr-Version: www-3.1 X-GNATS-Notify: >Number: 148138 >Category: kern >Synopsis: [zfs] zfs raidz pool commands freeze >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-fs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 25 12:40:00 UTC 2010 >Closed-Date: >Last-Modified: Sun Jun 27 04:18:53 UTC 2010 >Originator: Marcel Grandemange >Release: 8.0 Release >Organization: E-Soul Technologies >Environment: FreeBSD johan.thavinci.za.net 8.0-RELEASE-p3 FreeBSD 8.0-RELEASE-p3 #0: Tue May 25 20:54:11 UTC 2010 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Built a raidz in a vm, killed one drive booted up state was degraded. Replaced drive tried to rebuild no success with only some zfs related commands causing lock. After adding another drive and attemping to add it to current pool so i could try the zpool offline method, now all zpool related commands lock up and can't be ctrl-c or kill 9 or anything. Pool is uncontrollable now and i assume only way around is too recreate everything from scratch. [update] Even this isnt possible as zpool destroy tank also freezes some command results: [root@johan ~]# zpool status I do a CTRL-T load: 0.00 cmd: zpool 1061 [spa_namespace_lock] 4630.58r 0.00u 0.00s 0% 1756k load: 0.00 cmd: zpool 1061 [spa_namespace_lock] 5145.49r 0.00u 0.00s 0% 1756k and [root@johan ~]# zpool list load: 0.00 cmd: zpool 1257 [spa_namespace_lock] 2.03r 0.02u 0.00s 0% 1760k load: 0.00 cmd: zpool 1257 [spa_namespace_lock] 2.48r 0.02u 0.00s 0% 1760k and [root@johan ~]# zpool destroy tank load: 0.05 cmd: zpool 1262 [spa_namespace_lock] 46.71r 0.00u 0.00s 0% 1744k load: 0.05 cmd: zpool 1262 [spa_namespace_lock] 47.08r 0.00u 0.00s 0% 1744k >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 27 04:18:36 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=148138 >Unformatted: