http://bugzilla.suse.com/show_bug.cgi?id=966870 Peter Simons changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|LVM+LUKS encrypted root |LVM+LUKS encrypted root |partition created by |partition created by |Tumbleweed (and Leap) has |Tumbleweed (and Leap) has |on 10 GB space |only 10 GB space -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=966870 http://bugzilla.suse.com/show_bug.cgi?id=966870#c2 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #2 from Stefan Hundhammer --- This can be configured by the product manager in the product's control.xml file: Minimum and base size (the normal desired size) of the root file system as well as how much of the system volume group's disk space remains unallocated. I agree that these days a mere 10 GB is very small for a root file system, so this root base size might be increased somewhat. But this is a config parameter outside the scope of YaST. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=966870 http://bugzilla.suse.com/show_bug.cgi?id=966870#c4 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com Assignee|lnussel@suse.com |yast2-maintainers@suse.de --- Comment #4 from Ludwig Nussel --- TW and Leap behave differently here. On TW the maximum root fs size is 20GB while on Leap it's 10. The leap setting is inherited from SLE. With BTRFS the numbers change again. There we have a multiplication factor which is two for TW and four for Leap. So with BTRFS we get 40GB in both cases. Default size 20 and multiplication factor 2 might be more reasonable indeed. And now for the funny part which seems to be a bug. According to the documentation (https://github.com/yast/yast-storage/blob/master/doc/config.xml.description#...) the root filesystem maximum is meant to be applied only in case a separate home partition is proposed. Without separate home root would consume all space. Indeed that is the case without lvm. When enabling lvm the root size limit is applied even though no separate home is proposed. So whatever one may think about good default settings, at least the behavior is not consistent with the documentation :-) Back to YaST. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=966870 http://bugzilla.suse.com/show_bug.cgi?id=966870#c6 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #6 from Stefan Hundhammer --- AFAIK this clashes with the 'vm_desired_size' parameter. Not sure if the documentation for that one is 100% correct or even misleading; as I understood that one, it specifies how much of the total available volume group should be used for the proposal. The general idea is to not use all the available space so there is some available to resize any of the logical volumes. Arvin? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=966870 http://bugzilla.suse.com/show_bug.cgi?id=966870#c7 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aschnell@suse.com | |) | --- Comment #7 from Arvin Schnell --- AFAIS with LVM the root_base_size and root_max_size value is always used. So the documentation is wrong and should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=966870 http://bugzilla.suse.com/show_bug.cgi?id=966870#c12 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |ancor@suse.com Resolution|--- |FIXED --- Comment #12 from Ancor Gonzalez Sosa --- The desired/max/min sizes has been adapted for both Tumbleweed and Leap. Hopefully, having all provided feedback (like this bug) into account. So I'm closing this. Please reopen if you think this is still wrong in Leap 15.1 or in the current Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.