Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1, creating a hug volume in a pool with dir type
<volume>
<name>vol1</name>
<key>/tmp/dirpool/vol</key>
<capacity unit="G">30</capacity>
<allocation unit="G">30</allocation>
<target>
<path>/tmp/dirpool/vol</path>
<format type='raw'/>
</target>
</volume>
2 run the following commands:
# virsh vol-create dirpool ./voldirpool.xml & virsh vol-delete vol1 dirpool
[1] 26923
error: Failed to delete vol vol1
error: internal error volume 'vol1' is still being allocated.
it still reported internal error.
commit 618b55220ac0cfdbfb4fa4af6adf7631a9962397
Author: Dave Allan <dallan>
Date: Fri Jul 15 09:47:12 2011 -0400
Fix error code for storage operations
Many volume operations will fail if the volume in question is being
allocated. These operations were returning VIR_ERR_INTERNAL_ERROR
when they should be returning VIR_ERR_OPERATION_INVALID.
The bug has been verified on libvirt-0.9.4-rc1-1.el6
# virsh vol-create dirpool ./dirvol.xml & virsh vol-delete vol1 dirpool
[1] 19930
error: Failed to delete vol vol1
error: Requested operation is not valid: volume 'vol1' is still being allocated.
retest it on rc2 version, it is fixed.
libvirt-client-0.9.4-0rc2.el6.x86_64
libvirt-0.9.4-0rc2.el6.x86_64
# virsh vol-create dirpool ./dirvol.xml & virsh vol-delete vol1 dirpool
[1] 20311
error: Failed to delete vol vol1
error: Requested operation is not valid: volume 'vol1' is still being allocated.
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-2011-1513.html