Bug 949683 - Storage Live Migration of thick disk results in corrupted disk
Summary: Storage Live Migration of thick disk results in corrupted disk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.1.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.1.4
Assignee: Federico Simoncelli
QA Contact: Daniel Paikov
URL:
Whiteboard: storage
Depends On: 910445
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-08 18:48 UTC by Idith Tal-Kohen
Modified: 2016-02-10 18:52 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
During storage live migration a placeholder for the volumes was created inside the qcow header in the destination domain. The volumes being migrated inherited the temporary size of the placeholder, which was 10MB. When the space was exceeded, live migrating a preallocated file (for example, NFS) virtual disk to a different storage domain failed. Now, the volume is forcefully created using the sparse format in the destination domain. Preallocated file virtual disks can now be live migrated to different storage domains.
Clone Of: 910445
Environment:
Last Closed: 2013-05-01 18:25:11 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0774 0 normal SHIPPED_LIVE rhev 3.1.4 - vdsm bug fix update 2013-05-01 22:23:56 UTC
oVirt gerrit 12692 0 None None None Never

Comment 3 Daniel Paikov 2013-04-21 15:15:32 UTC 
Checked on vdsm-4.10.2-1.10.
Comment 6 errata-xmlrpc 2013-05-01 18:25:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0774.html
Note You need to log in before you can comment on or make changes to this bug.