Hmm…it probably is possible to alter it so it is longer a timeline or number snapshot. That would stop the cleanup service from touching it.
Would you mind opening an issue on gitlab for that so I don’t lose track of it?
Hmm…it probably is possible to alter it so it is longer a timeline or number snapshot. That would stop the cleanup service from touching it.
Would you mind opening an issue on gitlab for that so I don’t lose track of it?
Would you mind opening an issue on gitlab about that one too?
I just thought, maybe I go back to GRUB, but update system with a script, first command normal update, second command install GRUB anyway so just in case grub is updated I’m sure it will be installed and everything will run smoothly. (no problem installing it again even it is installed and no update I think- just to be “like normal”)
Feel free to check Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update - #1351 by limotux
Thank you.
Just for my understanding, what is this good for?
If you snapshot boot off a read-only snapshot, it won’t work fully and may not even let you login depending on what DM you are using.
This adds a r/w overlay on top of the read-only snapshot so you can successfully boot off of it.
right?
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont resume filesystems"
grub-btrfs-overlayfs
No, you need to put it in the HOOKS=
line between the "
btrfs-desktop-notification-git
, version r11.7b355ffjournalctl
added the option --dmesg
to monitor any new Btrfs messages in kernel log only.
The config /etc/btrfs-desktop-notification.conf
added a new configurable option LOG_LEVEL
.
See the doc about different log levels.
The default (recommand) LOG_LEVEL
is 4 (between lowest level: 0 and warning level: 4), the warning level message will show which identity file (with absolute file-path) is corrupted.
Why do I need snap-pac
if I have grub-btrfs
installed?
They do different things. grub-btrfs
populates the grub menu with your snapshots. snap-pac
takes snapshots during pacman operations.
Technically, you can use either, both or none. It just depends what you want to accomplish.
OK, thanks, I can do something with that.
I thinks you ask because of the “pacman -Qm” topic…
From AUR you have snap-pac-grub installed, wich you don’t need. but snap-pac is a regular package from the repo, that can be handy for snapshots.
What about this:
Good question… but @dalto says only pick one, an his first option is grub-btrfs
All right, then I’ll give it a try …
From my perspective, it doesn’t matter if you use snap-pac-grub
or enable the path unit. It is a matter of personal preference. Both should work.
The 2nd is easier for me to do .
One single Question, cause I never made that process before.
I have installed EOS with btrfs. The root partition contains subvolumes, but the home partition not. I need it cause I want to use timeshift to make snapshots from /home partition too.
The question is: Can I use your progamm to build subvolumes on my /home partition like /@home and it is easy to do? And if it works, do I have to copy the files from /home to the new @home subvolume manually per terminal? And are there any risks?
First, I should share that I don’t think your plan will work. I don’t think timeshift supports taking snapshots of multiple btrfs filesystems. Even if you create @home
on the other filesystem I think you will still have the same problem. Timeshift is very specialized tool and it is pretty limited in what it will do.
To answer your questions:
No.
It is easy to do even without a tool. sudo btrfs subvolume create /path/to/@home
You can copy them or just move them.
You need to be careful to maintain all the file permissions.
Thanks for your quick answer!
I will test it in a few days after backup all with clonezilla first.
But timeshift also includes snapshots of the home folder, but it has to be in the subvolume @home. But maybe you are right and the subvolume has to be at the same partition as @ (root). I don’t know. I will test it and post the results :-).