Project

General

Profile

Actions
Copy link

Bug #9678

open

ZFS panic when cancelling removal with Log Spacemap feature enabled

Added by Brad Lewis over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
Brad Lewis
Category:
-
Start date:
2018-07-26
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:

Description

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.

No data to display

Actions
Copy link

Also available in: Atom PDF