Re: [opensuse] How to undo snapper rollback?

15.04.2016 05:41, Chris Murphy пишет:

On Thu, Apr 14, 2016 at 10:47 AM, Andrei Borzenkov wrote:

...

14.04.2016 18:44, Moby пишет:

...

openSUSE Tumbleweed (20160411) (x86_64) system with / as btrfs. System was pretty much out of the box, with snapper taking snapshots etc with each zypper up etc.

Due to certain problems with some updates, I did a snapper rollback to a certain snapshot number. I realized after I did that that now I cannot delete one snapshot. This is the one that got set as the default subvolume when I did the snapper rollback. How do I put the system "back" to the way it was, where I had the ability to delete all snapshots.

You did not. Installation sets root to the first snapshot. It is probably always number 1, but I would be interested too in knowing how we can find out what root was before. This snapshot cannot be deleted just like your current root.

Maybe in /var/log/snapper.log

I think 1 refers to the subvolume path naming convention used by openSUSE.

Yes, and "snapper list" output.

nohostname:/ # btrfs sub list -t / ID gen top level path -- --- --------- ---- 257 627 5 .snapshots 258 823 257 .snapshots/1/snapshot

This one. ...

I don't see a rollback option in Snapper GUI. *shrug* Am I missing it?

Rollback as documented is really intended to be used from read-only snapshot boot. If something goes wrong you boot into one of existing read-only snapshots and then call "snapper rollback" to make it (well, its clone actually) your permanent root. So there is no GUI because you are never really supposed to use GUI. ...

OK moving on. Let's say I want to revert back to /1/ because I haven't rebooted or made any changes, so why not?

nohostname:/ # snapper rollback 1 Creating read-only snapshot of current system. (Snapshot 59.) Creating read-write snapshot of snapshot 1. (Snapshot 60.) Setting default subvolume to snapshot 60.

OK that's one way to do it I guess... Looks like there is no going back to the same filesystem tree/subvolume ID. But as it's a snapshot

Yes, which is one of things I actively do not like in SUSE implementation. Compare this with Solaris "boot environment" where you have multiple alternative versions of root and can switch between them (by "activating" boot environment).

it is pretty much the same thing. However, keep in mind that since I'm currently booted still in /1/ any changes now are going in /1/ and not into /60/ so I probably ought to reboot sooner than later.

Hmm, failed to start modem manager, failed to start network manager, failed to start avahi, lots of failures on the next boot. It's not exactly revealing why... OK force power off. Choose the last (probably

Sounds like a bug, although I am not sure to which extent this feature was tested ("rollback" from live system).

the oldest) read only snapshot from the GRUB menu. That works. But rootfs is readonly.

Of course. When you boot from snapshot in GRUB you boot into read-only subvolume.

So I'll try again, snapper rollback 1, and then reboot. Now it works.

So maybe the double rollback without rebooting confused something. *shrug* no worse for the wear though I guess.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org