Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The difference between snapper-rollback, and the default snapper rollback. #16

Open
konstantin1722 opened this issue Aug 1, 2023 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@konstantin1722
Copy link

I understand correctly that system rollback is possible only from a live image? I can make this conclusion because the readme file does not contain instructions for use, but it does contain a link to the arch wiki with a section where recovery is performed through a live image.

Can you tell me how your snapper-rollback differs from the default snapper rollback. Do they work the same way? I saw you mentioned OpenSUSE, but no specifics. I would be grateful for an answer or even a link to a resource where I can read it (arch wiki doesn't count).

@jrabinow
Copy link
Owner

jrabinow commented Aug 15, 2023

The difference between the built-in rollback and this script is that snapper can't make any assumptions around the partitions/subvolumes layout.
snapper rollback moves subvolumes and mounts them so that the system is rolled back but introduces techdebt: the subvolume layout becomes complex to work with, and this complexity increases every time the rollback is run.
snapper-rollback keeps the same exact subvolume layout, but the flipside is that it has to assume a specific partition layout.

This script can be run both from a live image and from a system installed to a hard drive. The only difference between running it from a hard drive and running it from a live image is the config file /etc/snapper-rollback.conf takes different values.

If you're looking for context around how things work, archwiki is the best resource: snapper-rollback just automates the wiki page.
If you're looking for context on the partition layout choice, I'd recommend going through this btrfs wiki page and this reddit thread

Good docs are important and take effort. Would creating a PR that updates the repo readme and/or adds a docs directory with what you've learned, make sense to help the next person asking these questions?

@jrabinow jrabinow added the documentation Improvements or additions to documentation label Aug 17, 2023
@konstantin1722
Copy link
Author

In that case, I will look into this issue soon and make an edit to the readme file.

I don't know how long this one's gonna take. But I think I can say I'm making a promise to do it.

@thebestcloudislocal
Copy link

thebestcloudislocal commented Oct 9, 2023

Another difference is that snapper-rollback leaves a @YYYY-MM-DDTHH:MM-subvolume forever, if I understand it correctly.
I have about ten @YYYY-MM-DDTHH:MM subvolumes now. Can I delete them? If so, how?

@jrabinow
Copy link
Owner

jrabinow commented Oct 9, 2023

@thebestcloudislocal yes, you can delete those as soon as you feel comfortable that your system is working as intended and that there's no data you'd like to recover from the old snapshot.

For deletion, simply mount the btrfs root partition anywhere you like and delete the snapshot just like you would delete any other snapshot. Please make sure to delete the right snapshot - once it's deleted, it's gone forever!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants