[Bug 1222465] fdisk creates broken partition table
https://bugzilla.suse.com/show_bug.cgi?id=1222465 https://bugzilla.suse.com/show_bug.cgi?id=1222465#c12 --- Comment #12 from Volker Kuhlmann <bugz57@top.geek.nz> ---
I know I'm talking to a wall but I'll try one last time:
Calm down. I am fixing it with urgency.
One person's alignment gap is the other person's free usable space.
Correct. Yast doesn't give options (it doesn't even say what it's doing), hence using other tools. Bad luck fdisk didn't flag user error. That's unix - everyone's allowed to be an idiot but doesn't have to be. With Redmond OS you must be an idiot, big brother always knows what you need.
So in light of this, am I correct assuming you tried to create a layout with 256 MiB manually with fdisk?
128MiB alignment, yes. Information I found suggests erase block sizes are much larger than 1MiB and flashbench testing indicates 128MiB to be a good choice.
Why aren't you using GPT where you can put your partitions one after another without gap, perfectly aligned?
If I knew everything, I could tell whether OtherOS on the earlier partitions still boots with GPT, but I don't. DOS tables are supposed to work on a 2TB disk so that seems the safe option. Plus it's always worked so far, so no change is safest.
There's two real issues: (1) fdisk should not allow such partitioning and
I prefer a warning, not error. There is often unexpected use in tools that eventually do what told. But whatever.
(2) parted should probably not just crash when it sees it.
Nothing is allowed to crash on bad input. Especially when it causes install failure. Show a warning, fine, a completely blank result with no reason why is not useful. I can recover now regardless whether anything gets fixed. Thanks for looking at it, I appreciate it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com