Bug 1571285

Summary:	RAW-Preallocated file-based disk convert to raw-sparse after cold migrating it to another storage domain
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Evelina Shames <eshames>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aefrat, appraprv, bugs, eshenitz, guillaume.pavese, tnisan
Target Milestone:	ovirt-4.3.3	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm-4.30.12, ovirt-engine-4.3.3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-16 13:58:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eyal Shenitzky 2018-04-24 12:50:06 UTC

Description of problem:

When cold migrating raw-preallocated file-based disk to a different file-based storage domain, the new disk create as RAW-Sparse instead of RAW-Preallocated.

After migrating the disk, it presented as "thin-provisioned" disk instead of "preallocated" and the disk actual size not equal to its provisional size (using qemu-img info).

There are two reasons for this bug:
1. The engine instructs the VDSM to create the raw-preallocated file-based disk as "sparse".
2. The vdsm use 'qemu-img convert' without the preallocation option (FALLOC).

Version-Release number of selected component (if applicable):
master-4.3.0 - from commit dd5c57f39e9ba031ae7abb734c33ee89965cc21c

How reproducible:
100%

Steps to Reproduce:
1. Create 2 GB raw-preallocated file-based disk
2. Migrate the disk from step 1 to different file-based disk

Actual results:
The disk becomes "thin-provisioned"

Expected results:
The disk should remain as "preallocated"

Additional info:

Comment 1 Eyal Shenitzky 2018-04-24 12:51:20 UTC

Relevant also when migrating preallocated block-based disk to file storage domain

Comment 2 Yaniv Kaul 2018-04-30 07:32:29 UTC

Severity?

Comment 3 Sandro Bonazzola 2019-01-28 09:34:26 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 4 Evelina Shames 2019-04-02 11:12:45 UTC

Verified on engine 4.3.3.1-0.1.

Comment 5 Sandro Bonazzola 2019-04-16 13:58:19 UTC

This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 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.