Bug 1105848 - Deleting snapshot does not free up block device Actual space allocation
Summary: Deleting snapshot does not free up block device Actual space allocation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.4.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.4.1
Assignee: Daniel Erez
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On: 1097819
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-08 07:50 UTC by rhev-integ
Modified: 2016-02-10 17:16 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, deleting a snapshot of block images/disks did not free up that snapshot's Actual space allocation on the VM image. Now, a fix enables the volume chain to be correctly prepared, and Actual space is updated to its expected size.
Clone Of: 1097819
Environment:
Last Closed: 2014-07-29 14:20:29 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-2014:0970 0 normal SHIPPED_LIVE vdsm 3.4.1 bug fix and enhancement update 2014-07-29 18:18:39 UTC
oVirt gerrit 28382 0 ovirt-3.4 MERGED blockVolume: prepare volumes for shrinkToOptimalSize Never

Comment 2 Aharon Canan 2014-06-26 08:22:30 UTC 
verified using 3.4.1 av10

Steps to Reproduce:
1. Create a vm with a disk on iscsi block device
2. Create around 4 snapshots - After each snapshot creation the Actual space of the image grows by 1 GB as expected
3. Delete the last snapshot
Comment 4 errata-xmlrpc 2014-07-29 14:20:29 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-2014-0970.html
Note You need to log in before you can comment on or make changes to this bug.