Install yabsnap on CachyOS
Btrfs automated snapshot manager.
From the official CachyOS repo. Install with pacman, no AUR helper needed.
Reviewed Nov 2, 2026 · independent guide
How do I install yabsnap on CachyOS?
Run this in a terminal:
sudo pacman -S yabsnapyabsnap is in the cachyos repo, the CachyOS project's own package repository, so pacman installs it directly with no AUR helper and no build script. The package is signed with the CachyOS repository key, and pacman checks the signature before it installs.
What should I do after installing yabsnap?
- Run yabsnap in a terminal.
- The package ships the systemd units yabsnap.service and yabsnap.timer. Read the project docs before you enable them.
- Run pacman -Qi yabsnap to see the installed version and the optional dependencies.
How do I update or remove yabsnap?
Update:
sudo pacman -SyuRemove:
sudo pacman -Rns yabsnapWhat is yabsnap?
Btrfs Scheduled Snapshot Manager for Arch.
Package description: Btrfs automated snapshot manager.
Reviews of yabsnap on CachyOS
No reviews yet. Be the first to review yabsnap.
From GitHub
hirak99/yabsnap · ★ 112 stars · last commit Oct 27, 2026
Real issues opened by users on the project's GitHub, shown as written with a link to each one. 10 most reacted issues opened in the last two years plus the 5 newest issues, bots, pull requests, non English and political posts skipped, capped at 15 per repo. Fetched Nov 1, 2026.
-
It's been raised a few times that there needs to be extensibility of Yabsna's functionality via user-scripts. This can help to implement simple to complex systems, for example - Post transaction hooks to btrfs sync the snapshot Rollback hook to add custom script Or complex…
- In `snap_operator.py`, the `_get_existing_snaps` method does not properly raise a `PermissionError`Closed
I tried to write test code for issue #47, but I found that the exception-raising code is not being executed correctly. Below is the relevant unit test code:
-
Based on #32, it should be now possible to implement rsync based snapshots. This will involve creating rsyncmechanism.py similar to btrfsmechanism.py.
- Cannot deleteClosed
created a config, tried deleting a snapshot and got this error. Switching to -git version, did not solve it.
-
I'm not able to create a rollback script due to the error attached below. My btrfs setup is as follows: Is this setup not supported by yabsnap currently, or is there something I'm doing wrong?
-
I have a mixed setup like: I recently did a rollback and noticed that I had to manually move C to the new filesystem. Are there any plans to automatically do this when performing a rollback?
- Multiple filesystems?Closed
Thank you for maintaining yabsnap! From reading the documentation I can't tell if yabsnap already supports multiple filesystems. For example, let's say there are three: (red, black, blue), and they're all btrfs filesystems. The existing documentation mentions…
- Identify errors when one configuration's prefix is a prefix of another configuration's prefixClosed
Maybe the title is a little hard to understand. For example, if one configuration is called root and the other is called root-user, then the contents of root-user will be displayed under root when listing.
-
What is be correct way to remove a config. If I know how to delete a config safely (not just rm -rf), I can take the snapshot on my physical machine and take much faster than #56 replied. Maybe others also want to know this.
-
While trying out and playing around with this tool, I stumbled across this error when generating the rollback script: $ run0 yabsnap --dry-run rollback-gen 20250523012845 Traceback (most recent call last): File " ", line 198, in runmoduleasmain File " ", line 88, in runcode File…
-
If snapshots are stored inside the live volume, rollback becomes problematic. Warn the user if this is the case. The warnings will appear during creation of snapshot. Will be displayed on console, or will go to the journal for automated snapshots. Why not fail? Because we do not…
-
A layout where btrfs snapshots are stored inside the live volume is problematic to roll back. Instead of still generating a script which will not succeed, we should fail loudly. Ref. Issue #90 and comments.
-
As support for nested subvolumes is limited the recommended subvol layout section in the README should mention that systemd will create two nested subvols /var/lib/{machines,portables}. It should be recommended to manually create them in a flat layout.
-
The TUI shows a non-zero exit error but never the reason for the error. Errors are only printed to tty. When the user tries to operate the TUI without sudo privileges its show some warning inside the TUI. For other errors the error message could just be printed inside the TUI.
-
With source = / and dest-prefix = /.snapshots/@/ I did not follow the dest-prefix example in the README but instead created directories for each subvol. The generated rollback script tries to move the active subvolume into itself: mv @ @/rollbackDATETIME@ What I would expect…
yabsnap on CachyOS: questions
Is yabsnap in the official CachyOS repo?
Yes. The yabsnap package is in the cachyos repo, version 2.4.6-1, built 2026-10-29. Install it with sudo pacman -S yabsnap.
Do I need an AUR helper for yabsnap?
No. It comes from the cachyos repo, so plain pacman installs and updates it, and sudo pacman -Syu keeps it current.
What is the yabsnap command?
yabsnap. The package is called yabsnap.