On Sun, Mar 8, 2015 at 10:12 AM, don fisher <hdf3@comcast.net> wrote:
I have not figured btrfs out yet. Why so many sub volumes.
Yeah I'm fairly non-charitable about this layout because it's non-obvious and there's no description anywhere. I'll explain it generally, because I don't know specifically why this layout was selected. First, the subvolume listing: boot/grub2/i386-pc boot/grub2/x86_64-efi opt srv tmp usr/local var/crash var/lib/mailman var/lib/named var/lib/pgsql var/log var/opt var/spool var/tmp .snapshots Inside of .snapshots, many additional snapshots: e.g. .snapshots/23/snapshot, .snapshots/24/snapshot, .snapshots/25/snapshot One reason for doing this is better granularity in taking snapshots and rollbacks, since at the moment only subvolumes can be snapshot. This is somewhat like using partitions but without the space limit consequences since subvolumes share all available pool space (quotas excepted). The other reason is that if you snapshot a subvolume, any snapshots in it are NOT snapshot. That is, there's no recursive snapshotting. But in practice I find the opensuse layout confusing. I'm also not a big fan of the .snapshot subvolume. Since it's navigable from / it means any old binaries with vulnerabilities are available for execution so some additional security precautions are probably going to be needed.
I am still trying to understand the philosophy of this design. Documentation exists as to what is there, but not why it is there:-(
It also confuses Fedora's installer, so you're not alone. After even a few hours and one software update, there are dozens of snapshots taken by snapper, and the Fedora installer sees them as dozens of unique openSUSE installations with no easy way to remove them. That's more of a real world collisions between two different strategies, rather than anything ill conceived about them though. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org