Comment # 5 on bug 1208437 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-workflow

That looks promising, indeed.