Bug 2104806 - Moving a compressed qcow to a block storage domain fails
Summary: Moving a compressed qcow to a block storage domain fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.5.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.5.2
: ---
Assignee: Benny Zlotnik
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-07 08:20 UTC by Benny Zlotnik
Modified: 2022-08-30 08:49 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.5.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-08 08:17:16 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.5?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 518 0 None Draft core: measure unattached disks 2022-07-07 08:21:41 UTC
Red Hat Issue Tracker RHV-47007 0 None None None 2022-07-07 08:22:44 UTC

Description Benny Zlotnik 2022-07-07 08:20:49 UTC 
Description of problem:
Moving a compressed qcow2 disk from a file storage domain to a block storage domain fails on lack of space on device, this happens because the LV is created too small to accommodate the uncomporessed qcow

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Import a compressed qcow2 from glance (fedora cloud image for example) to file SD
2. Move the disk to a block storage domain

Actual results:
Fails with an error like

qemu-img: error while writing at byte 799735808: No space left on device

Expected results:
Move completes

Additional info:
Comment 2 Sandro Bonazzola 2022-08-30 08:49:07 UTC 
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.2 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.
Note You need to log in before you can comment on or make changes to this bug.