Hello Chris and all, On 2015-07-20 T 10:35 -0600 Chris Murphy wrote:
The bootloader and its configuration could specify a subvolume to boot by path (which should always be relative to
, i.e. subvolid 5); or by subvolid, or by subvolume UUID. But none of those three are being done right now by (open)SUSE, instead a completely esoteric and hidden default subvolume switch is used, which totally masks how the system boots.
fortunately, that is not true. If you are booting into a read-only snapshot via Grub2, it is used what you are suggesting. Only if you advice snapper to make this current snapshot the permanent boot target (via "snapper rollback"), then the "btrfs subvol set-default" call is used (internally). It's neither esoteric nor hidden. My suggestion: don't touch the "btrfs" cmdline tool for snapshots, but do everything via "snapper", and you'll see some light:-)
The bottom line for Btrfs though, is scalability of subvolumes is still a problem apparently. Upstream is loosely saying in the realm of a few hundred subvolumes (which includes snapshots) is sane. Many hundreds or thousands are not a good idea. If it's sane to have 20 nspawn containers, each with their own subvolume, each with multiple snapshots, the idea of snapper doing recursive snapshots is rather premature because it easily means thousands of snapshots inside of a week.
Snapper does not do "recursive snapshots", as explained in other E-Mails already. It seems there is some mis-conception, how snapshots with snapper on btrfs work. And with respect to the number of snapshots: size is the limit. So long - MgE -- Matthias G. Eckermann - Senior Product Manager SUSE® Linux Enterprise SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org