How to take BTRFS Snapshots? Getting error in YasT

English Applications
#1

Hello!

I am a TTumbleWeed Newbie, coming from years of Fedora. Sadly, Fedora 32 is not an enjoyable experience, and I figured I’d try openSUSE Tumbleweed. So far, I am incredibly impressed. Example, installing the NVIDIA driver in Fedora is a pain, and there’s a few different ways to do it and it usually ends up in misery anyway. In OpenSUSE? Easy as pie!

Anyway, I tried to enable Snapshots, I have a BTRFs install, but I get this error.

Please advise.

Initial Screen:https://www.iheinrich.com/FirstWindow.png

Error Message: https://www.iheinrich.com/Error.png

I apologize if I made these images too large.

Any help would be appreciated.

All the best,

Heinrich Beck

#2

There has been a bug where systemd, after mounting file systems, then unmounts some of them. There are several threads about this. I’m suspecting that this may be happening to you.

#3

You may post your journal:

erlangen:~ # **journalctl -b --grep mount**
-- Logs begin at Sat 2020-04-25 11:03:30 CEST, end at Sat 2020-05-02 06:19:53 CEST. --
May 02 05:18:40 erlangen kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
May 02 05:18:40 erlangen kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
May 02 05:18:40 erlangen systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
May 02 05:18:41 erlangen systemd[1]: Mounting /sysroot...
May 02 05:18:41 erlangen systemd[1]: Mounted /sysroot.
May 02 05:18:41 erlangen systemd[1]: Condition check resulted in dracut mount hook being skipped.
May 02 05:18:42 erlangen systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
May 02 05:18:42 erlangen systemd[1]: Mounting Huge Pages File System...
May 02 05:18:42 erlangen systemd[1]: Mounting POSIX Message Queue File System...
May 02 05:18:42 erlangen systemd[1]: Mounting Kernel Debug File System...
May 02 05:18:42 erlangen systemd[1]: Mounting Kernel Trace File System...
May 02 05:18:42 erlangen systemd[1]: Starting Remount Root and Kernel File Systems...
May 02 05:18:42 erlangen systemd[1]: sysroot.mount: Succeeded.
May 02 05:18:42 erlangen systemd[1]: Mounted Huge Pages File System.
May 02 05:18:42 erlangen systemd[1]: Mounted POSIX Message Queue File System.
May 02 05:18:42 erlangen systemd[1]: Mounted Kernel Debug File System.
May 02 05:18:42 erlangen systemd[1]: Mounted Kernel Trace File System.
May 02 05:18:42 erlangen systemd[1]: Finished Remount Root and Kernel File Systems.
May 02 05:18:42 erlangen systemd[1]: Mounting /.snapshots...
May 02 05:18:42 erlangen systemd[1]: Mounting /boot/efi...
May 02 05:18:42 erlangen systemd[1]: Mounting /boot/grub2/i386-pc...
May 02 05:18:42 erlangen systemd[1]: boot-grub2-x86_64\x2defi.mount: Directory /boot/grub2/x86_64-efi to mount over is not empty, mounting anyway.
May 02 05:18:42 erlangen systemd[1]: Mounting /boot/grub2/x86_64-efi...
May 02 05:18:42 erlangen systemd[1]: Mounting /home...
May 02 05:18:42 erlangen systemd[1]: Mounting /home-HDD...
May 02 05:18:42 erlangen systemd[1]: Mounting /opt...
May 02 05:18:42 erlangen systemd[1]: Mounting /root...
May 02 05:18:42 erlangen kernel: EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Opts: (null)
May 02 05:18:42 erlangen systemd[1]: Mounting /srv...
May 02 05:18:42 erlangen kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May 02 05:18:42 erlangen systemd[1]: Mounting /tmp...
May 02 05:18:42 erlangen systemd[1]: Mounting /usr/local...
May 02 05:18:42 erlangen systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.
May 02 05:18:42 erlangen systemd[1]: Mounting /var...
May 02 05:18:42 erlangen systemd[1]: Mounted /.snapshots.
May 02 05:18:42 erlangen systemd[1]: Mounted /boot/efi.
May 02 05:18:42 erlangen systemd[1]: Mounted /boot/grub2/i386-pc.
May 02 05:18:42 erlangen systemd[1]: Mounted /boot/grub2/x86_64-efi.
May 02 05:18:42 erlangen systemd[1]: Mounted /home.
May 02 05:18:42 erlangen systemd[1]: Mounted /opt.
May 02 05:18:42 erlangen systemd[1]: Mounted /root.
May 02 05:18:42 erlangen systemd[1]: Mounted /srv.
May 02 05:18:42 erlangen systemd[1]: Mounted /tmp.
May 02 05:18:42 erlangen systemd[1]: Mounted /usr/local.
May 02 05:18:42 erlangen systemd[1]: Mounted /var.
May 02 05:18:42 erlangen kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
May 02 05:18:42 erlangen systemd[1]: Mounted /home-HDD.
May 02 05:18:54 erlangen systemd[1]: Mounting FUSE Control File System...
May 02 05:18:54 erlangen systemd[1]: Mounted FUSE Control File System.
May 02 05:19:02 erlangen systemd[1850]: run-user-477.mount: Succeeded.
May 02 05:19:02 erlangen systemd[1]: run-user-477.mount: Succeeded.
May 02 05:59:55 erlangen systemd[6787]: run-user-477.mount: Succeeded.
May 02 05:59:55 erlangen systemd[1850]: run-user-477.mount: Succeeded.
May 02 05:59:55 erlangen systemd[1]: run-user-477.mount: Succeeded.
erlangen:~ #
#4

I’d also encourage you to use the command line when running Snapper.
If the bug affects only the YaST tool, you can do the same with the command line.

Although you might think that using a graphical YaST tool would be easier,
Snapper is really so easy to use that it’s not different than what you see and do in the graphical tool.

As always,
The usual command line help file is a quick way to view available commands and options

snapper --help

But, if you want more conventional documentation, you can try
A Wiki FAQ
https://en.opensuse.org/openSUSE:Snapper_FAQ

SUSE documentation
Although SUSE is a different product and not all SUSE tools and methods will work in openSUSE, in this case they’re the same
https://documentation.suse.com/sles/11-SP4/html/SLES-all/cha-snapper.html

A Tutorial
https://en.opensuse.org/openSUSE:Snapper_Tutorial

HTH,
TSU