I recently set up Snapper for my system (following this guide that was linked in a previous topic I opened about it) for Fedora 34 and it’s doing its job, but I am currently having a hard time with the options. It looks like the scheduler does not clean up the timeline according to my settings, as I currently have 83 snapshots on my system:
$ sudo cat root
# subvolume to snapshot
# filesystem type
# btrfs qgroup for space aware cleanup algorithms
# fraction of the filesystems space the snapshots may use
# fraction of the filesystems space that should be free
# users and groups allowed to work with config
# sync users and groups from ALLOW_USERS and ALLOW_GROUPS to .snapshots
# start comparing pre- and post-snapshot in background after creating
# run daily number cleanup
# limit for number cleanup
# create hourly snapshots
# cleanup hourly snapshots after some time
# limits for timeline cleanup
# cleanup empty pre-post-pairs
# limits for empty pre-post-pair cleanup
Would you be able to point me towards what I am failing to set up?
Additionally (I would normally avoid 2 questions in one post, but they are related), I can’t get to work the bit that Chris Murphy’s mentioned in his post without messing up /etc/fstab/, so if you could please help with that it would be great.
According to the openSUSE Snapper Tutorial the cron scheduler is the default and the systemd service is an alternative. If the timeline snapshots are being made then presumably cron is running correctly?
@fbackstab have you checked in /var/log/snapper.log to see if there are any relevant error messages?
The only thing that looks like it is 2021-06-11 13:35:13 WAR libsnapper(38461) Client.cc(dispatch):1860 - CAUGHT: quota rescan or sync failed
Edit: apparently now it works (just took a while), so I suppose it’s been the systemd service. Now I have both activated, what shall I do? Deactivate the cronie scheduler and retain systemd or vice versa (i.e. fix the cronie one and use systemd as a temporary solution)?
I do not think I created one, is there any way I can check just to be sure?
$ sudo systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor pre>
Active: active (running) since Wed 2021-06-23 12:54:49 BST; 31min ago
Main PID: 1907 (crond)
Tasks: 1 (limit: 38022)
└─1907 /usr/sbin/crond -n
Jun 23 12:54:49 fedora crond: (CRON) INFO (RANDOM_DELAY will be scaled wi>
Jun 23 12:54:49 fedora crond: (CRON) INFO (running with inotify support)
Jun 23 13:01:01 fedora CROND: (root) CMD (run-parts /etc/cron.hourly)
Jun 23 13:01:01 fedora anacron: Anacron started on 2021-06-23
Jun 23 13:01:01 fedora anacron: Will run job `cron.daily' in 7 min.
Jun 23 13:01:01 fedora anacron: Jobs will be executed sequentially
Jun 23 13:01:01 fedora CROND: (root) CMDEND (run-parts /etc/cron.hourly)
Jun 23 13:08:01 fedora anacron: Job `cron.daily' started
Jun 23 13:08:01 fedora anacron: Job `cron.daily' terminated
Jun 23 13:08:01 fedora anacron: Normal exit (1 job run)