From owner-freebsd-fs@FreeBSD.ORG  Thu Apr 22 15:20:07 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4D511106564A
	for <freebsd-fs@hub.freebsd.org>; Thu, 22 Apr 2010 15:20:07 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 3CD2A8FC15
	for <freebsd-fs@hub.freebsd.org>; Thu, 22 Apr 2010 15:20:07 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3MFK7H7025909
	for <freebsd-fs@freefall.freebsd.org>; Thu, 22 Apr 2010 15:20:07 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3MFK7Uh025906;
	Thu, 22 Apr 2010 15:20:07 GMT (envelope-from gnats)
Date: Thu, 22 Apr 2010 15:20:07 GMT
Message-Id: <201004221520.o3MFK7Uh025906@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
From: Steve Polyack <korvus@comcast.net>
Cc: 
Subject: Re: kern/145339: [zfs] deadlock after detaching block device from
 raidz pool
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Steve Polyack <korvus@comcast.net>
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Apr 2010 15:20:07 -0000

The following reply was made to PR kern/145339; it has been noted by GNATS.

From: Steve Polyack <korvus@comcast.net>
To: bug-followup@FreeBSD.org, Alex.Bakhtin@gmail.com
Cc:  
Subject: Re: kern/145339: [zfs] deadlock after detaching block device from
 raidz pool
Date: Thu, 22 Apr 2010 11:13:26 -0400

 I've seen a similar issue in the past while testing hot-removal of RAIDZ 
 members (glabeled siis(4)-attached devices).  After the /dev/ada* entry 
 would disappear, the /dev/label/diskXX entry would remain and crash 
 shortly down the line with ZFS IO.  Here's the panic info in case it is 
 relevant:
 
 Fatal trap 12: page fault while in kernel mode
 cpuid = 2; apic id = 14
 fault virtual address   = 0x48
 fault code              = supervisor write data, page not present
 instruction pointer     = 0x20:0xffffffff8035f375
 stack pointer           = 0x28:0xffffff800006db60
 frame pointer           = 0x28:0xffffff800006db70
 code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags        = interrupt enabled, resume, IOPL = 0
 current process         = 2 (g_event)
 [thread pid 2 tid 100014 ]
 Stopped at      _mtx_lock_flags+0x15:   lock cmpxchgq   %rsi,0x18(%rdi)
 
 db> bt
 Tracing pid 2 tid 100014 td 0xffffff00014d4ab0
 _mtx_lock_flags() at _mtx_lock_flags+0x15
 vdev_geom_release() at vdev_geom_release+0x33
 vdev_geom_orphan() at vdev_geom_orphan+0x15c
 g_run_events() at g_run_events+0x104
 g_event_procbody() at g_event_procbody+0x55
 fork_exit() at fork_exit+0x118
 fork_trampoline() at fork_trampoline+0xe
 --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 ---