refactor(conf): Keep 10 important snaps, up from 5 (#1)
On an average daiy driver machine having 10 snaps would've allowed to roll back far enough into the past to work around: https://github.com/openzfs/zfs/issues/15526
This commit is contained in:
parent
31f5655ff0
commit
c686f7645f
@ -53,7 +53,7 @@ We retain two different snapshot chains, one for `pacman` transactions that only
|
||||
|
||||
Whenever an important package is affected by a transaction a snapshot goes into the corresponding chain. In all other cases - when an important package is not affected - snapshots go into the trivial chain.
|
||||
|
||||
The _trivial_ snapshot chain by default keeps 25 snapshots, the _important_ chain keeps 5. The thought process here is that you will likely not futz around with a kernel every day whereas you may very well install arbitrary packages multiple times a day. Snapshots should keep you safe for a couple of days hence the defaults of 5 and 25 snapshots, respectively.
|
||||
The _trivial_ snapshot chain by default keeps 25 snapshots, the _important_ chain keeps 10. The thought process here is that you will likely not futz around with a kernel every day whereas you may very well install arbitrary packages multiple times a day. Snapshots should keep you safe for a couple of days hence the defaults of 10 and 25 snapshots, respectively.
|
||||
|
||||
Snapshots may look like so:
|
||||
```
|
||||
|
@ -13,7 +13,7 @@ important_names='linux|systemd|zfs-(dkms|utils)'
|
||||
|
||||
# Number snapshots to keep
|
||||
snaps_trivial_keep='25'
|
||||
snaps_important_keep='5'
|
||||
snaps_important_keep='10'
|
||||
|
||||
# Which suffix to use in snapshot names to identify snapshots before a
|
||||
# trivial pacman operation and before important pacman operations.
|
||||
|
Loading…
x
Reference in New Issue
Block a user