You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From discussion in issue #19, there seems to be some interest in a rollback function.
Here's the current manpage description of rollback:
zfs rollback [-rRf] snapshot
Roll back the given dataset to a previous snapshot. When a dataset is rolled back, all
data that has changed since the snapshot is discarded, and the dataset reverts to the state at
the time of the snapshot. By default, the command refuses to roll back to a snapshot
other than the most recent one. In order to do so, all intermediate snapshots and bookmarks
must be destroyed by specifying the -r option.
The -rR options do not recursively destroy the child snapshots of a recursive snapshot.
Only direct snapshots of the specified filesystem are destroyed by either of these options.
To completely roll back a recursive snapshot, you must rollback the individual child snapshots.
-r
Destroy any snapshots and bookmarks more recent than the one specified.
-R
Recursively destroy any more recent snapshots and bookmarks, as well as any
clones of those snapshots.
-f
Used with the -R option to force an unmount of any clone file systems that are to
be destroyed.
This will be relatively straight forward to implement, I just want to be sure the UI gives ample warning of the destructive behavior of rolling back. The key thing for me is that intermediate snapshots must also be destroyed.
The text was updated successfully, but these errors were encountered:
From discussion in issue #19, there seems to be some interest in a rollback function.
Here's the current manpage description of rollback:
This will be relatively straight forward to implement, I just want to be sure the UI gives ample warning of the destructive behavior of rolling back. The key thing for me is that intermediate snapshots must also be destroyed.
The text was updated successfully, but these errors were encountered: