Bug 1502488
Summary: | Cold merge will fail if the base qcow2 image reports leaked cluster | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | nijin ashok <nashok> | |
Component: | vdsm | Assignee: | Ala Hino <ahino> | |
Status: | CLOSED ERRATA | QA Contact: | Raz Tamir <ratamir> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.1.6 | CC: | ahino, bburmest, dhuertas, gveitmic, lsurette, rabraham, ratamir, srevivo, tnisan, ycui, ykaul, ylavi | |
Target Milestone: | ovirt-4.2.0 | Keywords: | ZStream | |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
|
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Leaked clusters on an image are now correctly identified and handled, allowing cold merges to succeed when they are present.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1506503 (view as bug list) | Environment: | ||
Last Closed: | 2018-05-15 17:52:46 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1506503 |
Description
nijin ashok
2017-10-16 06:24:05 UTC
Ala, can we add a sentence or two about leaked clusters (what they are, how they happen, etc)? (In reply to Allon Mureinik from comment #3) > Ala, can we add a sentence or two about leaked clusters (what they are, how > they happen, etc)? I will it here rather than in the doctext: Leaked clusters could happen when qemu-kvm process is killed while the Vm is writing data. Leaked clusters mean waste of disk space, but no harm to data. Fixing leaks is possible by running qemu-img check -r leaks -------------------------------------- Tested with the following code: ---------------------------------------- ovirt-engine-4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos.noarch vdsm-4.20.6-62.gitd3023e4.el7.centos.x86_64 Tested with the following scenario: Steps to Reproduce: 1. Create a thin provisioned disk in RHV-M and assign to a VM. 2. Kill the qemu-kvm process while we write the data from the VM. While writing the data from the VM, the qcow2 will allocate new cluster and killing the process at this time will cause leaked cluster in the image. 3. Create a snapshot for the VM. 4. Do a cold merge. Actual results: Cold merge is completed successfully even when the image has leaked clusters Expected results: Moving to VERIFIED! 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. https://access.redhat.com/errata/RHEA-2018:1489 BZ<2>Jira Resync sync2jira sync2jira |