[BUG] about snapper-rollback HOT 4 CLOSED

Thanks, I've solved! A small note, after rollback if you want to access at your partition with all subvolume you must do:
mount -t btrfs -o subvolid=5 /dev/nvmeXpYnZ /your/mountpoint
instead
mount -t btrfs /dev/nvmeXpYnZ /your/mountpoint

from snapper-rollback.

Thanks for the detailed bug report! In step 2, try mounting /dev/nvme0n1p1 with -o subvolid=5 option instead of -o subvol=@
The reason for this is we're looking to get access to the btrfs root subvolume (subvolid=5), not the linux root (/), both of which are quite separate concepts. I'm afraid the terminology is rather confusing, but this is what the community has chosen. I'll encourage you to check the some terminology section in snapper-rollback.conf.

Also for step 3, you're looking for something like sudo snapper-rollback 5, without the SNAPID
Assuming you have a flat layout and that your snapper made a valid snapshot id 5, those 2 steps should be sufficient to get everything working again.

my doubt is, for rollback I must boot snapshot that I want to restore sure? Or I must boot on my root's partiton and restore from that?

As long as you can run the script and it has access to a mounted subvolid=5, you can boot from anything you'd like, it shouldn't matter.

from snapper-rollback.

Without the -o subvolid=5, mount will probably mount the default subvolume, which should be your linux root (@) so the -o subvolid=5 is indeed necessary.

Glad you were able to solve the issue!

from snapper-rollback.

It's all ok, now I can use snapper for restoring. If you want, you can close this issue

from snapper-rollback.