Bug 1298106

Summary: preserve sparseness for drive mirror operations over distributed storage
Product: Red Hat Enterprise Linux 7 Reporter: Jan Kurik <jkurik>
Component: qemu-kvm-rhevAssignee: Fam Zheng <famz>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: areis, dmaley, famz, huding, jkurik, juzhang, knoel, pbonzini, pbrady, pezhang, pkrempa, virt-maint, xfu
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1232914 Environment:
Last Closed: 2016-02-26 16:54:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1232914    
Bug Blocks:    

Description Jan Kurik 2016-01-13 09:06:02 UTC
This bug has been copied from bug #1232914 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 4 Fam Zheng 2016-01-19 09:12:48 UTC
To verify the bug, QE should test the blockdev-mirror command, which is introduced as a fix to this bug.

The command is going to be used in conjunction with blockdev-add.

Generally, all the existing drive-mirror cases apply to blockdev-mirror. In particular, what is wanted in this BZ is enabling zero detection feature by specifying "detect-zeroes=unmap" to the target image. The QMP pseudo command lines are:

    # blockdev-add {'options': {'node-name': 'target0', 'driver': 'raw',
    'detect-zeroes': 'unmap', 'file': {'driver': 'file', 'filename':

    blockdev-mirror {'device': 'd0', 'target': 'target0', 'sync': 'full'}

Comment 5 Peter Krempa 2016-02-04 16:48:13 UTC
blockdev-add can't be used by libvirt upstream at this point. I've noted this in the parent BZ. Moving back to ASSIGNED to track backport of the new required patches.

Comment 6 Ademar Reis 2016-02-26 16:54:36 UTC
We're withdrawing this from the z-stream because the fix is more complex than we anticipated. It'll be fixed in 7.3, but not in the z-stream (see bug #1232914).