Bug 755617

Summary: Rollbacks should be saved persistently on the disk after every change
Product: Red Hat Enterprise Linux 6 Reporter: Igor Lvovsky <ilvovsky>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: abaron, bazulay, iheim, lpeer, srevivo, syeghiay, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 755596 Environment:
Last Closed: 2011-11-22 13:01:14 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: 755596, 755620    
Bug Blocks:    

Description Igor Lvovsky 2011-11-21 15:37:23 UTC 
+++ This bug was initially created as a clone of Bug #755596 +++

Description of problem:
All rollbacks should be saved persistently on the disk after every change (especially after remove/clear recoveries)

Version-Release number of selected component (if applicable):


How reproducible:
Restart SPM during merge snapshots of large disks (with postzeroing), SPM will switched to another host and rollback the operation


Steps to Reproduce:
1. Two hosts, VM with snapshots and large disks (with postzeroing)
2. VM should be with RAW base volume (not template) and snapshot on it
3. Start delete snapshot and look for dd start in vdsm log
4. restart vdsm on SPM host
5. SPM will switch to another host and start rollbacks
  
Actual results:
Image will broken

Expected results:
No rollback should occurs on new SPM .


Additional info:

--- Additional comment from danken on 2011-11-21 10:21:42 EST ---

http://gerrit.ovirt.org/303
Comment 2 Igor Lvovsky 2011-11-22 13:01:14 UTC 

*** This bug has been marked as a duplicate of bug 755596 ***