Summary: | "zpool remove" causes panic: solaris assert: zio->io_type == ZIO_TYPE_WRITE (0x3 == 0x2) | ||
---|---|---|---|
Product: | Base System | Reporter: | Edward Tomasz Napierala <trasz> |
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> |
Status: | New --- | ||
Severity: | Affects Only Me | CC: | maurizio1018, mav, pstef |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Edward Tomasz Napierala
![]() ![]() Looks like this could be a fallout from r329732 "7614 zfs device evacuation/removal". I don't get a panic, but: : root@thinkpad:/tmp # zpool remove meh md0 load: 0.17 cmd: zpool 685 [spa_namespace_lock] 41.78r 0.00u 0.00s 0% 6288k mi_switch+0xbf _sx_xlock_hard+0x3d1 spa_open_common+0x3ac zfs_ioc_log_history+0x63 zfsdev_ioctl_common+0x503 zfsdev_ioctl+0x143 devfs_ioctl+0xc5 vn_ioctl+0x1a4 devfs_ioctl_f+0x1e kern_ioctl+0x25b sys_ioctl+0xf1 amd64_syscall+0x10c fast_syscall_common+0xf8 (In reply to Piotr Pawel Stefaniak from comment #2) After a while: # zpool status meh pool: meh state: ONLINE remove: Removal of vdev 0 copied 47.5K in 1h0m, completed on Thu Apr 21 19:58:42 2022 144 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM meh ONLINE 0 0 0 md1 ONLINE 0 0 0 errors: No known data errors |