Date: Fri, 16 Apr 2010 20:10:03 GMT From: Andriy Gapon <avg@icyb.net.ua> To: freebsd-fs@FreeBSD.org Subject: Re: kern/145339: [zfs] deadlock after detaching block device from raidz pool Message-ID: <201004162010.o3GKA3gH082758@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/145339; it has been noted by GNATS. From: Andriy Gapon <avg@icyb.net.ua> To: bug-followup@FreeBSD.org, Alex.Bakhtin@gmail.com Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: kern/145339: [zfs] deadlock after detaching block device from raidz pool Date: Fri, 16 Apr 2010 23:09:38 +0300 Are you sure that this is a deadlock? If yes, could you please describe what you see in more details. I am asking because to me it seems like a NULL pointer crash: > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x48 It looks like perhaps zio->io_vd became NULL while an I/O response was traveling up and vdev_geom_io_intr was not prepared to handle that. > _mtx_lock_flags() at _mtx_lock_flags+0x39 > vdev_geom_io_intr() at vdev_geom_io_intr+0x62 > g_io_schedule_up() at g_io_schedule_up+0xed > g_up_procbody() at g_up_procbody+0x6f > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201004162010.o3GKA3gH082758>