It's possible for the following assertion to be tripped when running ztest:
assertion failed for thread 0xf09fca40, thread-id 549: spa->spa_max_ashift == spa->spa_min_ashift (0xc == 0x9), file ../../../uts/common/fs/zfs/vdev_removal.c, line 965 > $c libc.so.1`_lwp_kill+7(ebdde6c0, ebdde6c0, a9, fee7865e) libc.so.1`_assfail+0x214(ebddea28, fed7ac3c, 3c5, fef62000) libc.so.1`assfail3+0xde(fed7b130, c, 0, fed812cb, 9, 0) libzpool.so.1`spa_vdev_copy_impl+0x26b(89a4b40, ebddef74, ebddef68, 8992dc0, ebe10a00, fef073c0) libzpool.so.1`spa_vdev_remove_thread+0x6cd(87450c0, 0, 0, fee8f43a) libc.so.1`_thrp_setup+0x8c(f09fca40) libc.so.1`_lwp_start(f09fca40, 0, 0, 0, 0, 0) > ::spa -v ADDR STATE NAME 08723000 ACTIVE ztest ADDR STATE AUX DESCRIPTION 087466c0 HEALTHY - root 087450c0 HEALTHY - /rpool/tmp/ztest.0a 08745640 HEALTHY - indirect 08745bc0 HEALTHY - /rpool/tmp/ztest.2a 08746140 HEALTHY - /rpool/tmp/ztest.3a - - - spares 08744b40 HEALTHY - /rpool/tmp/ztest.spares.0 The problem is that spa_min_ashift and spa_max_ashift need to ignore spare devices. Upstream bugs: DLPX-34624 You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/543 -- Commit Summary -- * 9084 ztest failure: spa->spa_ max_ashift == spa->spa_min_ashift (0xc == 0x9) -- File Changes -- M usr/src/uts/common/fs/zfs/vdev.c (5) -- Patch Links -- https://github.com/openzfs/openzfs/pull/543.patch https://github.com/openzfs/openzfs/pull/543.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/543 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/Tc301bb7b6adf50d7-M52f2629a61b65bc5e871c7f3 Powered by Topicbox: https://topicbox.com