Reviewed by: Matt Ahrens <[email protected]> Reviewed by: Prashanth Sreenivasa <[email protected]> Reviewed by: John Kennedy <[email protected]>
This panic was hit three times during device removal tests: vdev_indirect_mark_obsolete+0xc8(ffffff03885a6000, 20003000, 800) free_mapped_segment_cb+0x2e(ffffff03885a6000, 20003000, 800) range_tree_vacate+0x65(ffffff0377aca2c0, fffffffff7a6ec10, ffffff03885a6000) spa_vdev_remove_cancel_sync+0x110(0, ffffff0376a27d00) dsl_sync_task_sync+0xda(ffffff00103c1a70, ffffff0376a27d00) dsl_pool_sync+0x2a5(ffffff03b1d80240, be) spa_sync_iterate_to_convergence+0xf7(ffffff039a7b8000, ffffff03bfe7a1c0) spa_sync+0x2b9(ffffff039a7b8000, be) txg_sync_thread+0x23f(ffffff03b1d80240) thread_start+8 The sync task that cancels the removal must know about unflushed allocs and frees in the metaslabs of the device being removed. Upstream bug: DLPX-57783 You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/672 -- Commit Summary -- * 9678 ZFS panic when cancelling removal with Log Spacemap feature enabled -- File Changes -- M usr/src/pkg/manifests/system-test-zfstest.mf (1) A usr/src/test/zfs-tests/tests/functional/removal/removal_cancel.ksh (105) M usr/src/test/zfs-tests/tests/functional/removal/removal_resume_export.ksh (2) M usr/src/uts/common/fs/zfs/vdev_removal.c (5) -- Patch Links -- https://github.com/openzfs/openzfs/pull/672.patch https://github.com/openzfs/openzfs/pull/672.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/672 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/T2e02251f67952d17-Mbff1fcfe6cfc26051ae1a288 Delivery options: https://openzfs.topicbox.com/groups/developer/subscription
