The setting "TIMELINE_LIMIT_HOURLY" is not tied to the timer frequency
Regarding this box in the article:
Note: The configuration parameter TIMELINE_LIMIT_HOURLY is tied to the above setting. In the above example it now refers to how many 5-minute snapshots are kept.
I am currently trying out snapper. I found out that although my snapper-timeline.timer runs every 15 minutes the cleanup job only keeps hourly snapshots. The quoted box seems false to me. TIMELINE_LIMIT_HOURLY is not tied to the timer frequency. Note that the TIMELINE_MIN_AGE setting lets the last few of my 15 minute snapshots persist on cleanup which can lead to misunderstandings. —This unsigned comment is by DonRichie (talk) 04:16, 13 January 2018. Please sign your posts with ~~~~!
Duplicate snapshots subvolume when using "snapper create-config"
The section "Suggested filesystem layout > Configuration of snapper and mount point" suggests to create a subvolume
@snapshots and mount it at
snapper create-config additionally creates a new subvolume we end up with two subvolumes, but only one of them used. And to do it we need to unmount the manually created subvolume first, then run
create-config and then remount it again. Otherwise
create-config fails because the path
/.snapshots already exists.
If this interpretation is correct, should we maybe recommend creating the snapper config manually instead? By adding a file to
/etc/snapper/configs/ and referencing it in
/etc/conf.d/snapper. That way the creation of the subvolume can be prevented and the umount/mount dance is not needed.
Njam (talk) 18:10, 3 February 2018 (UTC)
- You do end up with two subvolumes (one at
@snapshotsand one created by snapper). Just delete the snapshot created by
snapper create-configin this case. -- Rdeckard (talk) 18:21, 3 February 2018 (UTC)