zfs recv -F should destroy any snapshots created since the incremental source
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).
Updated by Christopher Siden about 6 years ago
- Status changed from In Progress to Closed
commit 34f2f8c Author: Matthew Ahrens <email@example.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 <firstname.lastname@example.org> Reviewed by: Adam Leventhal <email@example.com> Reviewed by: Peng Dai <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com>