-
Notifications
You must be signed in to change notification settings - Fork 1.2k
linstor: use sparse/discard qemu-img convert on thin devices #11787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linstor: use sparse/discard qemu-img convert on thin devices #11787
Conversation
This reduces revert time and also makes the devices not thick allocated anymore.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## 4.19 #11787 +/- ##
=========================================
Coverage 15.18% 15.18%
- Complexity 11370 11371 +1
=========================================
Files 5415 5415
Lines 476082 476089 +7
Branches 58129 58130 +1
=========================================
+ Hits 72288 72299 +11
+ Misses 395702 395698 -4
Partials 8092 8092
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
harikrishna-patnala
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM
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?