Hello, (hmm, should we open a board-support mailinglist? ;-) Am Samstag, 27. April 2019, 09:40:03 CEST schrieb Axel Braun:
I updated TW this morning, and now it looks like this (shortened):
# | Typ | before# | Date | Space | Descript. -----+--------+---------+--------------------+------------+----------- -- 0 | single | | | | current 549* | single | | Sa 30 Mär 21:17:16 | 21,11 MiB | 573 | post | 568 | Mo 22 Apr 10:12:32 | 25,21 MiB | 574 | pre | | Fr 26 Apr 19:04:58 | 368,00 KiB | zypp(zypper) 575 | post | 574 | Fr 26 Apr 19:05:02 | 208,00 KiB | 576 | pre | | Fr 26 Apr 19:38:44 | 192,00 KiB | yast fonts 577 | post | 576 | Fr 26 Apr 19:39:09 | 384,00 KiB | 578 | pre | | Fr 26 Apr 19:39:18 | 96,00 KiB | yast sudo 579 | post | 578 | Fr 26 Apr 19:39:51 | 16,00 KiB | 580 | pre | | Fr 26 Apr 19:39:58 | 16,00 KiB | yast alt. 581 | post | 580 | Fr 26 Apr 19:40:10 | 816,00 KiB | 582 | pre | | Sa 27 Apr 08:33:06 | 11,93 MiB | zypp(zypper) 583 | post | 582 | Sa 27 Apr 08:43:46 | 10,82 MiB |
That gives some insghts: - Still 549 is mounted!
Yes, of course. When using the "usual"/"traditional" setup, you can think of the additional snapshots as "backups" that are done before and after installing packages etc. As every good backup, they are hopefully superfluous and get thrown away sooner or later ;-) The snapshot that gets used will only change if you use "snapper rollback". (And I guess you used "snapper rollback" in the past, because otherwise you'd have #1 instead of #549 mounted at /.) The longer version of this is on https://www.susecon.com/doc/2015/sessions/HO20031.pdf (which I abused ;-) for a btrfs talk in my LUG recently - thanks Thorsten!) There's also the option to use transactional updates which means the running system is read-only [1][2], and a new read-write snapshot gets created when/where package updates etc. get applied. Afterwards, the default snapshot gets switched to the newly created (and updated) snapshot, and after a reboot that new snapshot gets mounted. Note that the slides mentioned above are from 201 and therefore don't include transactional updates yet. You'll need to google Richard's slides for more details ;-)
- 574/575 are from a removal of some packages. - 576-581 result from starting some YaST modules *without performing changes*. This is IMHO nonsense, aka a bug - there is no need for a snapshot unless I changes something
Agreed in theory. In practise, some YaST modules do their changes not only at the very end, but also if you click specific buttons, so creating a snapshot at the end would be too late. This also means that doing the snapshots when starting and exiting a YaST module is the easiest way. I wouldn't be surprised if this is done in the "global" YaST code and not even module-specific. That said - if you want to get rid of these superfluous snapshots, feel free to open a bugreport - I'd say it's a valid bug ;-) On the positive side, creating a "superfluous" snapshot is "cheap", so there'n not too much harm done.
- 582/583 are from the zypper dup. Here my expectation - based on above comments - would have been that this becomes the bootable snapshot, or the current snapshot.
That would happen if you'd use transactional updates. Regards, Christian Boltz [1] That's slightly simplified, I'll ignore overlayfs for now [2] Kubic uses transactional updates by default, but you can also switch Tumbleweed and Leap to operate in this way. -- Aber doch ... Woast Bub, ich denk bei sowas immer willkürlich an den Worst-case. Nämlich das das nicht ein Gscheidle wie du macht, sondern daß das irgendeiner hier oder in irgendeinem Forum aufschnappt. [David Haller in opensuse-de] -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org