linstor: use sparse/discard qemu-img convert on thin devices #11787
+59
−40
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.
Description
Instead of always write zeroes to the drbd device, we enable now sparse/discard options for qemu-img convert,
if the Linstor device supports thin.
This reduces revert time and also makes the devices not thick allocated anymore.
Too ensure the devices only contains zeroes, we have to blkdiscard it before.
Fixes: #11765
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Tested local volume revert on a Linstor cluster.
This change should only affect Linstor primary storage, as no other code parts are touched.
How did you try to break this feature and the system with this change?