https://bugzilla.suse.com/show_bug.cgi?id=1208437 https://bugzilla.suse.com/show_bug.cgi?id=1208437#c3 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ancor@suse.com) | --- Comment #3 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Martin Wilck from comment #2)
Note that the primary issue here is IMO that running the guided setup does not remedy the situation, although the error message suggests that it would.
Well. It suggests to run the Guided Setup to adjust the settings and try again. It doesn't guarantee there is a set of settings that will work for your case and your desires. ;-)
It would also be very helpful if the constraints from control.xml were transparent in the guided setup. For example, if there was a label or tool tip next to the "enable snapshots" check box saying "enabling snapshots requires at least xyz GB of disk space".
That's indeed the main problem here. There is no guidance in the UI about how each setting affects the size of the needed partitions. Especially the "enable snapshots" one, which may have a huge impact (in the concrete case of Leap, it increases the requirement for the root partition in a 250%). Giving a good overview is quite hard. Almost any setting (enabling a separate home, enabling snapshots, adjusting the RAM size...) can have an impact in several of the proposed file-systems. And those impacts vary from one combination of product+role to another. We are trying an alternative approach in D-Installer that should make the implications of every change way more visible. See https://github.com/yast/d-installer/blob/master/doc/storage_ui.md#general-wo... Of course, we don't need to go that far in YaST. Showing some label about what's the min size for "/" or about how the presence of snapshots multiplies the min size (as said, by 3.5x in the case of Leap) would already help people to figure out what is wrong. On the other hand and based on priorities, I wouldn't promise that will happen in the short term. :-( -- You are receiving this mail because: You are on the CC list for the bug.