Don't try to get mg of hole vdev in removal #17080
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
When doing device removal, we verify that the vdev being removed isn't the last vdev in the normal class. To do that, we iterate over all the disks and checking their metaslab class until we find one in the normal group. Right now, if you have a hole vdev before the first allocatable normal class vdev, we kernel panic.
Description
Add a check for hole vdevs to the passivate code.
How Has This Been Tested?
Added a new test to the test suite and verified that it passes. Without the change, it fails.
Types of changes
Checklist:
Signed-off-by
.