You are not logged in.
Pages: 1
I spent the afternoon playing with Snapper on a btrfs formatted VM, and I have to say, it's pretty darn slick. This is my first experience with drive snapshots. Wow. Cool stuff.
So then I decided to install Snapper on my main machine. The only difference is it has a LUKS encrypted drive. The installation produced no errors, but when I try to initialize a config directory it balks, saying that /sbin/chsnap is not installed.
I've been googling, but I can find zero information on what chsnap is. I also can't find any information on whether snapshots even work on encrypted drives. I assume they would, since the kernel is doing the decryption before anything else happens.
Has anyone else encounter this particular error?
Offline
How are you trying to initialize the config directory? Also, where have you installed snapper from? Arch Linux packages don't install anything to /sbin anyway.
Not an installation issue, moving to "Newbie Corner".
Offline
Installed via the standard pacman -S snapper
Initializing it via:
snapper -c root create-config /
That's what triggers the error. On a non-ecrypted install it works great.
Offline
chsnap is only ever used if your root is ext4.
https://github.com/openSUSE/snapper/blo … xt4.cc#L62
https://bugzilla.novell.com/show_bug.cgi?id=725995#c20
If your root isn't ext4, then check what wipefs reports the filesystem as, perhaps you have the remnants of an older filesystem still present.
(Note that, despite it's scary name, wipefs does not wipe filesystems unless you explicitly tell it to. Check the manpage)
If your root isn't ext4, and wipefs confirms there isn't an ext4 signature present, you should probably file a bug upstream.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1