Following this topic on the MLO forum , I realised that there might be a flaw in the "simple" partitioning scheme that we now use , though the flaw was likely already there before but less critical.
The partitioner checks for "min_hd_size => MB(51200)" to determine whether it should split / and /home. The problem described on the MLO forum is that when resizing a Windows partition of a 64 GB disk (thus freeing 20 GB for Mageia), the split partitioning was used, which does not make sense in 20 GB of disk space.
- S: réservé au SystÃ¨me : 100 M
- C: Windows : 64 G
- D: DATA : 84 G
Proposed partitioning by the installer:
- sda2: C: Windows : 44 G
- sda5: linux native : 6.4 G (/)
- sda6: swap : 1.2 G
- sda7: linux native : 12 G (/home)
We need to ensure that the split partitioning is used when the free disk space is => MB(51200), not the overall hard disk size.
Steps to Reproduce:
Not putting as a release blocker so close to the release, so it will probably have to do with errata.
Rémi, could you write the Errata entry if you think it's worth one?
As it's been a long time since the release and I don't plan to write an errata entry for Mageia 5 now, I remove the corresponding tag (I admit it's mostly due to laziness and not to the fact that the issue is not relevant ;) though it is kind of a corner case).
Setting as release blocker for Mageia 6 though.
Pascal, Thierry or other developers, is it a bug you think you can fix for Mageia 6? It's quite a nasty one although a corner case so should happen rarely.
Nasty bug but corner case for small disks. Needs decision from Mageia tools group on whether to keep as release blocker or not.QA Contact:
(In reply to Samuel Verschelde from comment #4)
> Pascal, Thierry or other developers, is it a bug you think you can fix for
> Mageia 6? It's quite a nasty one although a corner case so should happen
Ping. If we don't plan to work on it right now, the priority could be decreased and the milestone set to Mageia 7.
No answer from anyone, lowering priority.