https://bugzilla.suse.com/show_bug.cgi?id=1208437 https://bugzilla.suse.com/show_bug.cgi?id=1208437#c1 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com Flags| |needinfo?(ancor@suse.com) Severity|Normal |Minor --- Comment #1 from Stefan Hundhammer --- We have certain criteria that must be met for certain storage layouts. One of them is a minimum amount of free disk space, configured in control.xml on the installation medium on a per-product basis, to enable features like Btrfs snapshots. Of course, as always, once we start being so configurable, more and more config options and criteria keep coming from all sides; and at some point, the clear error message that we once had is so watered down that it doesn't tell anybody anything. I guess this is what happened here. Ancor? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1208437 https://bugzilla.suse.com/show_bug.cgi?id=1208437#c3 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ancor@suse.com) | --- Comment #3 from Ancor Gonzalez Sosa --- (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.

https://bugzilla.suse.com/show_bug.cgi?id=1208437 https://bugzilla.suse.com/show_bug.cgi?id=1208437#c5 --- Comment #5 from Martin Wilck --- Ack(In reply to Ancor Gonzalez Sosa from comment #3)

(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. ;-)

The problem was that the guided setup didn't offer any settings that I could have used to fix the issue.

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%).

Yes, I think that's the fallout of dozens of bug reports about ENOSPC issues with btrfs. And there's no clean solution, because how much space is really required depends on snapper settings, frequency of system updates, overall installatoin size, the weather, and whatnot. In a minimal installation, 10G can be just fine *with* snapshots, while elsewhere 100G can be tight. I think that at least if the guided setup logic decides that a certain option is greyed out / unavailable, it should provide a hint to the user, telling her the reason. If the logic is too complex to untangle and display to the user in an understable fashion, maybe the complex logic itself is the issue?

See https://github.com/yast/d-installer/blob/master/doc/storage_ui.md#general-wo...

That looks promising, indeed. -- You are receiving this mail because: You are on the CC list for the bug.