On Fri, Jul 17, 2015 at 7:23 AM, Arvin Schnell
On Thu, Jul 16, 2015 at 10:11:03AM -0600, Chris Murphy wrote:
On Thu, Jul 16, 2015 at 9:44 AM, Richard Brown
wrote: 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.
I agree. And if systemd creates that subvolume it also has to add it to fstab just like YaST and snapper do with the subvolumes they create.
The problem with that is there's no standardization or agreement yet
on how to organize Btrfs subvolumes. Upstream has been fairly clear in
the Btrfs wiki and linux-btrfs@ that it's preferable to
a. put subvolumes only in subvolid 5, and assemble them via fstab,
rather than nesting
b. not put any system root on subvolid 5, rather those should go in
their own subvolume (subvolid 5 cannot be (re)named or deleted so its
purpose is neither discoverable or removable)
c. not have utilities changing the default subvolume since that's a
user domain (and user space changeable) shortcut feature
SUSE is totally contrary to a, b, and c. And as a consequence you
can't expect systemd to create