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
Some times it's helpful to be able to create a snapshot from the
bootloader, outside of the OS. On the snapshot screen, there's now a
MOD+N option to create a (N)ew snapshot. It rides along the coat-tails
of most of the snapshot cloning/duplication logic, as that has checks
for everything we also care about.
The MOD+S handler in zfsbootmenu.sh has grown quite large, with the
creation of quite a few global variables. The bulk of this is now hidden
inside snapshot_dispatcher(), which can use local variables for all of
the space calculations.
Copy file name to clipboardExpand all lines: pod/online/snapshot-management.pod
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,12 @@ This creates a boot environment from a snapshot with out modifying snapshot inhe
37
37
38
38
The operation will fail gracefully if the pool can not be set I<read/write>.
39
39
40
+
=item I<[MOD+N]> B<snapshot creation>
41
+
42
+
This creates a new snapshot of the currently selected boot environment. A new snapshot is useful if you need to repair a boot environment from a chroot, to allow for easy roll-back of the changes.
43
+
44
+
The operation will fail gracefully if the pool can not be set I<read/write>.
45
+
40
46
=item I<[MOD+D]> B<diff>
41
47
42
48
Compare the differences between snapshots and filesystems. A single snapshot can be selected and a diff will be generated between that and the current state of the filesystem. Two snapshots can be selected (and deselected) with the tab key and a diff will be generated between them.
0 commit comments