On Wed, Jul 15, 2015 at 6:11 PM, Johannes Ernst <johannes.er...@gmail.com> wrote:
> Cleaning this all up is a bit of pain, and > btrfs subvolume delete -r dir > would solve it nicely. It's come up before: http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg42455.html http://lists.freedesktop.org/archives/systemd-devel/2015-April/030297.html I'm concerned about the interaction of machinectl snapshots of its own subvolumes, and rpm-ostree, and snapper snapshots. The only really convincing argument for tested subvolumes I've read is as an explicit break from being included in the snapshotting above it in the hierarchy. So the /var/lib/machines organization burdens other projects or users with the problem of how / or /var is snapshot and then a rollback happens, how to properly reassemble the system that includes /var/lib/machines subvolumes that are now in a different tree. How does this all get located and assembled properly at boot time? How is all of this backed up properly? How is it restored properly? I think recursive snapshotting and subvolume deletion is not a good idea. I think it's a complicated and inelegant work around for improper subvolume organization. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
