backend: fix zero-numberio in dry-run #2015
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.
In offline verification, io_hist_tree is not saved to the state file, so
io_u->numberiois always zero in the second job (the verify phase). To address this,do_dry_run()simulates the saved WRITE job and logs io_u entries into io_hist_tree vialog_io_piece(). The issue is thatio_u->numberiois always zero when passed to log_io_piece().To reproduce this issue, run the following jobs in turn.
Fixes: #2013