Description of problem: when you try to delete a Snapshot which has a parent disk bigger than the remaining Space in the Storage Pool, the request fails with: Cannot remove Snapshot. Low disk space on Storage Domain Version-Release number of selected component (if applicable): ovirt-engine-3.6.3.4-1.el7.centos.noarch vdsm-4.17.24-0.el7.centos.noarch How reproducible: always Steps to Reproduce: 1.create am VM with a Disk preallocated bigger than 50% of the remaining Space in the Storage Domain 2.create a live Snapshot 3.try to delete the Snapshot live. Actual results: Snaphot will not be deleted, because not enought Space is available to completely copy the whole Disk to a new one (which is still the behaviour of offline Snapshot Deletion) Expected results: Snapshot will be deleted, because no Storage Extension is required with live merge / blockcommit anymore Additional info: I think the Problem is that the calcution of the required free Space is still using the offline Snapshot restrictions. This behaviour is a Problem when you use Snapshots for backing up big VMs (Fileserver etc.) as you always required the double Space of the VM in the Pool, but this Space cannot be used for VM disks.
Vered, as storage space validations was your feature, can you please have a look?
Reason for requesting a blocker: It renders the merge operation impossible in case of extremely large disks when a small snapshot was made for backup purposes, cold merge will sometimes will not be possible due to disk space restrictions leaving live merge as the only option since it only requires a space equal to the small snapshot size rather than the big base image." QE - ACK?
Ala, as this is a user facing issue, please add some doctext to explain this bugfix.
verified on rhevm-3.6.5.3-0.1.el6.noarch. this operation is now blocked due to lack of space on the target storage domain, oVirt's ui prompts the user with a pop up warning.
Tested with ovirt-engine-3.6.6.2-1.el7.centos.noarch, seems to be fixed.
(In reply to md from comment #5) > Tested with ovirt-engine-3.6.6.2-1.el7.centos.noarch, seems to be fixed. Not sure why this wasn't moved automatically, but it's indeed fixed, closing.