amd64/148138: zfs raidz pool commands freeze

[Marcel Grandemange]

>Number:         148138
>Category:       amd64
>Synopsis:       zfs raidz pool commands freeze
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>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:
>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 at 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 at 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 at 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 at 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:
>Unformatted: