Project

General

Profile

Bug #3888

zfs recv -F should destroy any snapshots created since the incremental source

Added by Christopher Siden about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Category:
zfs - Zettabyte File System
Start date:
2013-07-15
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

When 'zfs recv -F' is used with an incremental recv it rolls back any changes made since the last snapshot in case new changes were made to the file system while the recv is in progress (without -F the recv would fail when it does it's final check to commit the recv-ed data as the recv-ed data conflicts with the newly written data).

However, if there is a snapshot taken after the recv began rolling back to the 'latest' snapshot will not help and the recv will still fail. 'zfs recv -F' should be extended to destroy any snapshots created since the source snapshot when finishing the recv (effectively rolling back through all snapshots, instead of just to the latest snapshot).

History

#1

Updated by Christopher Siden about 6 years ago

  • Status changed from In Progress to Closed
commit 34f2f8c
Author: Matthew Ahrens <mahrens@delphix.com>
Date:   Mon Jul 29 11:55:16 2013

    3888 zfs recv -F should destroy any snapshots created since the incremental source
    Reviewed by: George Wilson <george.wilson@delphix.com>
    Reviewed by: Adam Leventhal <ahl@delphix.com>
    Reviewed by: Peng Dai <peng.dai@delphix.com>
    Approved by: Richard Lowe <richlowe@richlowe.net>

Also available in: Atom PDF