Op vrijdag 26 april 2019 19:38:21 CEST schreef Axel Braun: That confused me too. The way I understand it now, is that the mounted one is what's currently (:D) running. And 0 is definitely the initial install, shows that on TW and Leap. In a couple of weeks I'll have a look after dupping 15.0 -> 15.1. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

Hello, (hmm, should we open a board-support mailinglist? ;-) Am Samstag, 27. April 2019, 09:40:03 CEST schrieb Axel Braun: 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 ;-) 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. 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(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

On 27/04/2019 21.35, Dave Howorth wrote: If there are no changes, the snapshot doesn't take space. Except metadata or however it is called. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

On 28/04/2019 12.19, Dave Howorth wrote: I suppose it is easier to code. One snapshot at entry, another at exit. But you are right, if there are no changes it adds complexity to the list. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

On Sat, 27 Apr 2019 21:57:07 +0200 Knurpht-openSUSE <knurpht(a)opensuse.org> wrote: Ah, thanks. That makes it clear to me ;) -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org