Description of problem: 'blockVolume -> calculate_volume_alloc_size' contains a validation to prevent specifying initial_size for preallocated volumes. It should be removed as creating qcow volumes on preallocated is needed for restoring from incremental backup.
Daniel, can you describe the use case for this? I think the only use case is restoring the base volume created using preallocated qcow2 format, when the size of the volume is bigger than the virtual size (due to qcow2 metadata). For snapshots we always use sparse format and never pre-allocated, right?
(In reply to Nir Soffer from comment #1) > Daniel, can you describe the use case for this? > > I think the only use case is restoring the base volume created using > preallocated qcow2 format, when the size of the volume is bigger than > the virtual size (due to qcow2 metadata). > > For snapshots we always use sparse format and never pre-allocated, right? Right, on snapshot creation, engine always creates a sparse format volume.
Hi Daniel, Is there an easy user scenario to verify this bug?
Hi Daniel, Please provide a clear scenario for verification, thanks.
(In reply to Evelina Shames from comment #4) > Hi Daniel, > Please provide a clear scenario for verification, thanks. You can verify by creating a preallocated cow disk on a block domain with a specified initial size (and incremental backup enabled). E.g.: POST /ovirt-engine/api/disks <disk> <sparse>false</sparse> <format>cow</format> <backup>incremental</backup> <initial_size>1024</initial_size> <provisioned_size>1024</provisioned_size> <storage_domains> <storage_domain> <name>block</name> </storage_domain> </storage_domains> </disk>
Verified on engine-4.4.0-0.13.master.el7
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.