Bug 755617 - Rollbacks should be saved persistently on the disk after every change
Summary: Rollbacks should be saved persistently on the disk after every change
Keywords:
Status: CLOSED DUPLICATE of bug 755596
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On: 755596 755620
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 15:37 UTC by Igor Lvovsky
Modified: 2016-04-18 06:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 755596
Environment:
Last Closed: 2011-11-22 13:01:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.