[Bug 229007] [zfs] kernel crashes on remove disk

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Oct 11 15:58:31 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229007

--- Comment #9 from Jeremy Faulkner <gldisater at gmail.com> ---
tar zcvf core-dump-zfs-devrem.tar.gz /boot/kernel /usr/lib/debug/boot/kernel
/var/crash/*.0

https://drive.google.com/open?id=1SUTm-hBgIhkkTmYNridU9zZqVMSIlA3T

root at devremoval:~ # uname -a
FreeBSD devremoval 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338859 GENERIC  amd64

I haven't updated this bhyve vm recently but it's been unable to boot if three
of it's drives are enabled.


panic: solaris assert: zio->io_type == ZIO_TYPE_WRITE (0x3 == 0x2), file:
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_indirect.c, line:
1267
cpuid = 1
time = 1539270204
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe004d1677e0
vpanic() at vpanic+0x1a3/frame 0xfffffe004d167840
panic() at panic+0x43/frame 0xfffffe004d1678a0
assfail3() at assfail3+0x2c/frame 0xfffffe004d1678c0
vdev_indirect_io_start() at vdev_indirect_io_start+0xae/frame
0xfffffe004d167900
zio_vdev_io_start() at zio_vdev_io_start+0x4b5/frame 0xfffffe004d167960
zio_execute() at zio_execute+0x18c/frame 0xfffffe004d1679b0
zio_nowait() at zio_nowait+0xc4/frame 0xfffffe004d1679e0
vdev_mirror_io_start() at vdev_mirror_io_start+0x42a/frame 0xfffffe004d167a70
zio_vdev_io_start() at zio_vdev_io_start+0x1fe/frame 0xfffffe004d167ad0
zio_execute() at zio_execute+0x18c/frame 0xfffffe004d167b20
taskqueue_run_locked() at taskqueue_run_locked+0x10c/frame 0xfffffe004d167b80
taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe004d167bb0
fork_exit() at fork_exit+0x84/frame 0xfffffe004d167bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe004d167bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 0 tid 100510 ]
Stopped at      kdb_enter+0x3b: movq    $0,kdb_why
db>

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-fs mailing list