Hi Arvin snapper --ambit classic rollback does work! no segfault! and when I NOW repeat just $ snapper rollback Ambit is classic. Creating read-only snapshot of default subvolume. (Snapshot 303.) Creating read-write snapshot of current subvolume. (Snapshot 304.) Setting default subvolume to snapshot 304. Seems that I am now in "ambit-classic"-mode althoug I have no idea what it means. Trying: # snapper --ambit transactional rollback Ambit is transactional. Segmentation fault (core dumped) which seems to be a remaining error ANYHOW .. thanks for the help. I can rollback again! Thank you Christian Am 10.07.20 um 13:35 schrieb Arvin Schnell:
On Fri, Jul 10, 2020 at 01:27:27PM +0200, Christian Mahr wrote:
Hi
I have an up-to-date Tumbleweed maintuaned 20200708 - and tried today to rollback to an earlier snapshot to check for some effect on some other program - and got a segfault!
to demonstrate this issue I typed:
snapper create -t single -d "test rollback" snapper rollback
and got a "Segmentation fault (core dumped)" on the rollback command.
Creating snapshots and deleting does work. The same segfault happens also with every number of snapshot I specify. I checked also the root file system for potential btrfs problem :
btrfs check --force /dev/sdb3
which showed no error. Am I the only one observing this with the recent Tumbleweed? What to check? any suggestion? Try 'snapper --ambit classic rollback'.
And always provide the complete console output.
ciao Arvin
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org