On 2024-03-19 11:07, Roger Oberholtzer wrote:
Top post here as it is the solution..
I once again have access to the computer. I have retried Andrei's suggestion:
snapper --ambit=classic rollback
OK, you can ignore half of my earlier post now :D I'm glad this worked out for you.
I am still confused why the snapshots before 1405/1406 went away. They were there at one point when I rebooted. After the reboot they were
The only way those should have gone away by themselves is if snapper deleted them. You can find the rules for this (see man snapper-config): hadron:~ # snapper get-config Key | Value -----------------------+------ ALLOW_GROUPS | ALLOW_USERS | BACKGROUND_COMPARISON | yes EMPTY_PRE_POST_CLEANUP | yes EMPTY_PRE_POST_MIN_AGE | 1800 FREE_LIMIT | 0.2 FSTYPE | btrfs NUMBER_CLEANUP | yes NUMBER_LIMIT | 2-10 NUMBER_LIMIT_IMPORTANT | 4-10 NUMBER_MIN_AGE | 1800 QGROUP | 1/0 SPACE_LIMIT | 0.5 SUBVOLUME | / SYNC_ACL | no TIMELINE_CLEANUP | yes TIMELINE_CREATE | no TIMELINE_LIMIT_DAILY | 10 TIMELINE_LIMIT_HOURLY | 10 TIMELINE_LIMIT_MONTHLY | 10 TIMELINE_LIMIT_WEEKLY | 0 TIMELINE_LIMIT_YEARLY | 10 TIMELINE_MIN_AGE | 1800 The number limit settings are the important ones here. A minimum of 4, maximum of 10, important snapshots will be retained, and a minimum of 2, maximum of 10, others will also be retained. The two options are effected separately. Without seeing the results of snapper list before all this happened, it is impossible to know just what was deleted, and why. It seems that, when you removed snapshots, you deleted all the important ones. That leaves the unimportant ones; unless 1405/1406 were the only unimportant ones left, I would expect to be seeing more of them. Anyway, it's all water under the bridge now, and you seem to be back with a working system -- so just mark it down as one of life's greater mysteries, and carry on :D
in the situation I was in: only one snapshot - making it difficult to use that snapshot for anything. Especially not a rollback. Unless you know about the mystical --ambit=classic option.
There's an excellent (;) ) description of that option in the snapper manpage: -a, --ambit ambit Operate in the specified ambit. Can be used to override the ambit detection. Allowed ambits are auto, classic and transactional. Clearly just another example of why programmers should never be allowed to write software documentation :) Now, if you are feeling brave, log in on a text console (Ctrl-Alt-F1) and re-run zypper dup, as has been suggested. Personally, with all the information now available on this, if I were to do this I would drop into non-graphical most (init 3) before doing the dup, and switch back to graphical mode. But that's just me and my very cautious character. For example, it was years before I fully trusted the stability of drpm, zypper and btrfs. I'm not quite as bad as the Amish, though -- I do have a telephone, and I do drive a car :D