On Thu, Jul 16, 2015 at 9:44 AM, Richard Brown
Are you actually sure that the snapshots of /var/lib/machines are being managed and messed up by snapper?
It's not being messed up by snapper, it's messed up by not having an fstab entry that causes persistence in the contents of /var/lib/machines.
Everything you said sounded reasonable right up until you said " I'm pretty sure the following will happen:"
It's a logical argument because I don't happen to have either a Factory installation right now, or an fstab from a Factory installation. But I have a 13.2 installation so I'm familiar with the openSUSE fstab, and I have a Fedora 22 which has systemd 219 and it creates subvolumes for containers at /var/lib/machines/. Since a btrfs snapshot will stop at that subvolume, none of the nspawn containers will be in any of the snapshots of /. And because fstab doesn't contain either a /var or /var/lib or a /var/lib/machines mount point, there is no persistence of /var/lib/machines - systemd will see it's missing in any rollback and create a new subvolume there, which will be empty. So yes your containers will vanish, unless I'm missing something, and I don't think I am or I wouldn't have started the thread.
I think we should look into fixing it if is IS broken..but I think you're mistaken Snapper only backs up and restores the *root* subvolume, / by default
Snapper rollback depends on the fstab being properly populated to do rollbacks.
Any other subvolumes can be snapper snapshotted and restored, but they'll be ignored and *not emptied* when snapper restores the *root* subvolume
Are you pontificating a possible problem, or actually saying that the behaviour of snapper breaks with systemd 219 and nspawn containers?
I am hypothesizing based on available facts. But I find your pompous third way of asking the same question entertaining. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org