879780 – vol-clone failed to clone LVM volumes

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 879780 - vol-clone failed to clone LVM volumes

Summary: vol-clone failed to clone LVM volumes

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	libvirt
Sub Component:
Version:	6.4
Hardware:	All
OS:	All
Priority:	unspecified
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Ján Tomko
QA Contact:	Virtualization Bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	881827
TreeView+	depends on / blocked

Reported:	2012-11-24 10:20 UTC by János Tamási
Modified:	2013-02-21 07:27 UTC (History)
CC List:	9 users (show)
Fixed In Version:	libvirt-0.10.2-10.el6
Doc Type:	Bug Fix
Doc Text:	Cause: A cleanup in virStorageBackendLogicalCreateVol removed the setting of volume type. Consequence: Volume was treated as a file without a format and libvirt was unable to clone it. Fix: Set the volume type. Result: Logical volumes can be cloned.
Clone Of:
Environment:
Last Closed:	2013-02-21 07:27:42 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0276	0	normal	SHIPPED_LIVE	Moderate: libvirt security, bug fix, and enhancement update	2013-02-20 21:18:26 UTC

Description János Tamási 2012-11-24 10:20:27 UTC

Description of problem:
After upgrading libvirt from 0.9.10 to 1.0.0 vol-clone is not working anymore with LVM volumes. Downgrading libvirt to the latest 0.9 series (0.9.13) works fine.

Version-Release number of selected component (if applicable):
libvirt 1.0.0
qemu 1.2

How reproducible:
clone an existing LVM volume: vol-clone --pool storage vs1 vs12

Actual results:
virsh # vol-clone --pool storage vs1 vs12
error: Failed to clone vol from vs1
error: belső hiba: Child process (/usr/bin/qemu-img convert -f raw -O none /dev/storage/vs1 /dev/storage/vs12) unexpected exit status 1: 2012-11-24 10:10:25.786+0000: 20306: debug : virFileClose:72 : Closed fd 27
2012-11-24 10:10:25.786+0000: 20306: debug : virFileClose:72 : Closed fd 29
2012-11-24 10:10:25.786+0000: 20306: debug : virFileClose:72 : Closed fd 25
2012-11-24 10:10:25.786+0000: 20306: debug : virCommandHook:2119 : Hook is done 0
qemu-img: Unknown file format 'none'

Comment 2 Ján Tomko 2012-11-25 02:06:00 UTC

Reproducible with libvirt-0.10.2-9.el6 as well.

Proposed upstream patch:
https://www.redhat.com/archives/libvir-list/2012-November/msg01055.html

Comment 3 Ján Tomko 2012-11-26 13:28:00 UTC

Fixed upstream by:
commit 70f0bbe8e046dae1b811378f735872d3e61f4609
Author:     Ján Tomko <jtomko>
AuthorDate: 2012-11-25 02:59:33 +0100
Commit:     Michal Privoznik <mprivozn>
CommitDate: 2012-11-26 14:01:29 +0100

    storage: fix logical volume cloning

Downstream backport:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-November/msg00266.html

Comment 5 zhe peng 2012-11-30 06:06:48 UTC

I can reproduce this with build:
libvirt-0.10.2-9.el6.x86_64

verify with:
libvirt-0.10.2-10.el6.x86_64

step:
  1: create a lvm pool
 # virsh pool-dumpxml lvm
<pool type='logical'>
  <name>lvm</name>
  <uuid>a2dc4aad-ff27-41d5-f598-612dbfe91620</uuid>
  <capacity unit='bytes'>20967325696</capacity>
  <allocation unit='bytes'>11811160064</allocation>
  <available unit='bytes'>9156165632</available>
  <source>
    <device path='/dev/sda2'/>
    <name>vg_virt</name>
    <format type='lvm2'/>
  </source>
  <target>
    <path>/dev/vg_virt</path>
    <permissions>
      <mode>0755</mode>
      <owner>-1</owner>
      <group>-1</group>
    </permissions>
  </target>
</pool>
  2: clone lvm vol
  # virsh vol-clone --pool lvm vgtest1 vgtest3
Vol vgtest3 cloned from vgtest1
  
  # virsh vol-list lvm
Name                 Path                                    
-----------------------------------------             
vgtest1              /dev/vg_virt/vgtest1                    
vgtest2              /dev/vg_virt/vgtest2                    
vgtest3              /dev/vg_virt/vgtest3 
 
  vgtest3 created w/o error, verification passed.

Comment 6 errata-xmlrpc 2013-02-21 07:27:42 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/RHSA-2013-0276.html

Note You need to log in before you can comment on or make changes to this bug.