Incorrect maximum DVA value in DDE_GET_NDVAS() #7234
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.
The conditional was reversed which caused garbage values to be used when
calculating dds_ref_dsize.
Description
Fixed the conditional.
Motivation and Context
Discovered while porting the vdev evacuation code. This problem caused bogus values to be stored both in-core and on-disk for dds_ref_dsize which should show up in, for example,
zpool status -D <pool>
as wild values forDSIZE
. It has the effect of, among other things, causingdsl_pool_adjustedsize()
to return bogus values.How Has This Been Tested?
I used the following reproducer script and observed the value of DSIZE:
Types of changes
Checklist:
Signed-off-by
.