They are set up automatically on OpenSUSE and make a new snapshot before and after every program installation, update and removal. Awesome for general peace of mind and especially when you’re up to strange shenanigans.
Also, for people on distros that don’t have an OOTB solution like OpenSUSE have, I recommend snapper and btrfs-assistant. You just install both packages, open the assistant GUI and create a profile for your root partition.
You can then also install a snapper plugin for your package manager, if one exists (I know DNF and pacman have one), which automatically take pre/post snapshots like OpenSUSE does, so you can quickly roll back if something goes wrong after a particular update/install/removal.
I’ve been using the above with EndeavourOS for a year now and it’s come in very handy on a couple of occasions.
Me:
- make the snapshot after the system is already broken
- Break it more
- Don’t restore the snapshot because its old and you can fix it
Been using it on a fedora workstation and a Debian server for 2 years and it has been stable and amazing for backups and regressions. So fast and easy to use. I use timeshift to handle organizing and scheduled backups.
FWIW, I set up these distros to separate my home directory from the OS, so backups aren’t clogged with random files in my /home directory. I use Pika Backup to handle the /home directories to a separate backup site.
It’s basically automated, reliable, and sooo fast. Love it.
The FS feature is great, it’s just cumbersome to use without a tool.
Snapper works well for a local backup like history both against botched updates and accidental deletion, but eats up the free space with the default settings.
Timeshift is an easy to use GUI but doesn’t support non-default partitions.
Also the quota support had a nasty side effect: freezing the whole system on snapshot deletion.
But It’s just a corrupt driver dude, I know I can fix it.
I don’t now how to use them but have btrfs snapshots set up by default on SUSE nonetheless
Used them to debug a problem. Forgot to remove them. Wondered why I ran out of disk space a few weeks later.
Very good. Saved me a couple of times. It’s a really hassle free way of preventing update fuckery
They’re set up in Nobara by default, haven’t had to use them yet but every once in a while I see them in the journalctl and get a warm feeling.
Snapshots are definitely a hit or miss with me. I nearly never use them, but when I need to recover a file it’s awesome. The only system related problem I had with Nvidia drivers but it was actually better to reinstall so it does all the install configuration itself
Although the most problems I had with it is backup of data. I tend to hoard too much
I’ve been using snapshots for a couple of years. So far I’ve only had to restore a snapshot once, but it and it worked fine. The snapshots are created almost instantly and they don’t use much disk space unless a lot of stuff has been changed.
Too confusing, why can I create them with one command but not restore them in the same way? Last time I was gonna use them to fix an issue I spent an hour trying to figure out how to restore it and then just ended up fixing the issue manually in much less time.
Why dont you just use timeshift ?
Missed previous highway exit:
Use Debian stable / Ubuntu LTS
If you use btrfs snapshots and systemd-boot instead of grub, then be carefull restoring updates from before a kernel update.
If I understand it correctly, with systemd-boot the kernel lives in the EFI partition, while the kernel modules live in the main (btrfs) partition. If you restore a snapshot with a different kernel version, it doesn’t restore the kernel itself, but the kernel modules have different filenames, which stops the system from being able to boot.
At least that is my understanding of the problem, from having to debug it twice (just start a live-boot system and use Timeshift to restore the system to after the update again). The next time I install Linux, I think I’ll go with grub instead of systemd-boot.
That being said, I really like btrfs snapshots as a sort of “almost backup” (still do regular backups on an external drive). They are quick and easy, and most packet managers can be setup to automatically make a snapshot before installing/updating stuff.
The kernel in the EFI partition is used as a tool to bootstrap hardware and memory for your proper kernel, which is chainloaded.
There is a simple reason for that: The Linux kernel can do anything a bootloader needs to do, especially for itself, so why not use it as one?
That said, in most setups there is another bootloader before that, which loads the kernel itself and the initramfs for that kernel. That can be for example systemd-boot, formerly known gummiboot, a minimal bootloader meant to (auto-)discover EFI compatible stuff it can load.
Dracut creates a setup / boot chain like that.
Thanks for explaining it! So systemd-boot finds the kernel in the EFI partition, which it then loads, and then that kernel loads another kernel from the main partition, which is then the full OS.
Is there a reason it’s done this way, and not just the bootloader loads the main kernel?
Also, are the two kernels the same, or does this use two different kernels?
Sorry for the late reply btw, responses were broken for me
No problem, thanks for replying.
In the case of Dracut, I’m not sure what it does exactly, but the kernels will almost definitely not be identical. In the “EFI kernel”, uneeded modules (meaning most of them) are usually omitted.
You could probably also have different kernels in terms of version number, although it might complicate things. Kinda depends on whether they recycle data structures from the first kernel and whether those remain compatible. I don’t really know whether this is actually done tho.
The reason why multiple kernels (or bootloaders for that matter) are used is that there are different levels of “readiness” in your system. Say you have LVM and a LUKS encrypted partition (in whatever order). Systemctl-boot will load the kernel and it’s initramfs, but can’t be bothered to deal with complicated file system shenanigans. That would complicate the whole program significantly.
So it just loads a Linux kernel which has these capabilities. That kernel can deal with LVM, decrypt the LUKS partition (or ask for a password), mount whatever btrfs nonsense is inside and then hand it over to the proper kernel. The proper kernel can in turn rely on having all its stuff mounted and ready, instead of having to worry about all this.
You could do with just one kernel, but Dracut allows you to rapidly create bootable kernel + initramfs pairs of which you might need multiple (e.g. for dual booting, backup). Moreover, you probably wouldn’t really want it to fiddle with your kernel all the time, especially when it’s customised already.
That makes sense. It looks like a really clever way of letting the boot process allow for basically any arangement. Thanks!
They work.
