Skip to content
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

Do not change qcow+preallocated volumes when moving disks #875

Merged
merged 1 commit into from
Jul 25, 2023

Conversation

ahadas
Copy link
Member

@ahadas ahadas commented Jul 18, 2023

Base volumes can be of QCOW format and preallocated type when the disk is set with incremental-backup enabled. When moving disks, we now propagate the incremental-backup settings forward to CreateVolume so it will keep these volumes preallocated on the destination storage domain.

Bug-Url: https://bugzilla.redhat.com/2211608

Base volumes can be of QCOW format and preallocated type when the disk
is set with incremental-backup enabled. When moving disks, we now
propagate the incremental-backup settings forward to CreateVolume so it
will keep these volumes preallocated on the destination storage domain.

Bug-Url: https://bugzilla.redhat.com/2211608

Signed-off-by: Arik Hadas <ahadas@redhat.com>
@ahadas
Copy link
Member Author

ahadas commented Jul 18, 2023

Base volumes can be of QCOW format and preallocated type when the disk is set with incremental-backup enabled. When moving disks, we now propagate the incremental-backup settings forward to CreateVolume so it will keep these volumes preallocated on the destination storage domain.

Bug-Url: https://bugzilla.redhat.com/2211608

@bennyz that's my theory but I didn't check it yet (FYI)

@bennyz
Copy link
Member

bennyz commented Jul 19, 2023

Base volumes can be of QCOW format and preallocated type when the disk is set with incremental-backup enabled. When moving disks, we now propagate the incremental-backup settings forward to CreateVolume so it will keep these volumes preallocated on the destination storage domain.
Bug-Url: bugzilla.redhat.com/2211608

@bennyz that's my theory but I didn't check it yet (FYI)

Makes sense to me, worth a try

@ahadas
Copy link
Member Author

ahadas commented Jul 23, 2023

verified, this change indeed keeps the base volume with qcow+preallocated configuration on the host side and also converts base volume that have been switched to qcow+sparse back to qcow+preallocated when they move again while the guest keeps functioning well. now need to see what's going on with OST...

@ahadas
Copy link
Member Author

ahadas commented Jul 24, 2023

/ost

@ahadas ahadas merged commit c4fe7d6 into oVirt:master Jul 25, 2023
4 checks passed
@ahadas ahadas deleted the bug_2211608 branch July 25, 2023 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants