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)
- I just found it a bit confusing procedure - probably because I'm just learning about btrfs. I've opened a ticket on snapper to allow skipping the creation of the subvolume: https://github.com/openSUSE/snapper/issues/390 Maybe that would make it simpler. -- Njam (talk) 19:04, 3 February 2018 (UTC)
Backup non-btrfs boot partition on pacman transactions
The hook suggested in this section is not unique to Snapper (or Btrfs), and could be useful in other configurations. Perhaps it should be moved to Backup or EFI System Partition. —This unsigned comment is by DCengineer (talk) 05:41, 26 June 2018 (UTC). Please sign your posts with ~~~~!
New article structure
Thinking about adding two new subsections (modify and delete configurations), I observed the structure of the article was not grouped. Could be better to change article structure to (e.g.):
1 Installation 2 Configuration 2.1 Create a new configuration 2.2 List configurations 2.3 Modify a configuration (new subsection -> snapper -c config set-config option=value) 2.4 Delete a configuration (new subsection -> snapper -c config delete-config) 3 Snapshots 3.1 Take snapshots 3.1.1 Automatic timeline snapshots 22.214.171.124 Enable/disable 126.96.36.199 Set snapshot limits 188.8.131.52 Change snapshot and cleanup frequencies 3.1.2 Manual snapshots 184.108.40.206 Simple snapshots 220.127.116.11 Pre/post snapshots 3.1.3 Snapshots on boot 3.2 List snapshots 3.3 Delete a snapshot 4 Access for non-root users 5 Tips and tricks [... same as original ...]
New page suggestion: Btrfs Snapshots
The main article about Btrfs is already very long but does not cover the tools for working with snapshots, even though some of these tools are already in the repositories, and are popular. There is this article about Snapper, that covers some of these tools, but the article about snapper should focus on Snapper itself, and maybe tools based on snapper, but not independent tools. It is also important to show which tools are based on snapper and which tools only require btrfs itself. The Snapper article mixes both tools. -- Teateawhy (talk) 03:09, 11 January 2020 (UTC)