| Summary: | resizing partition generated unexplained "move right" operation | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | skierpage <info> |
| Component: | general | Assignee: | Volker Lanz <vl> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
skierpage
2010-09-02 03:31:24 UTC
Thank you for taking the time to file this elaborate and detailed bug report. I agree the wording "move left" or "move right" for moving partitions is not perfect, but I cannot come up with a better solution right now. I'm not convinced "move the start of the partition further away from the beginning of the device" is that much of an improvement. The mysterious move you encountered in your use case is indeed due to the application making sure the partition table follows the MS-DOS cylinder boundary conventions. See http://blog.volker-lanz.de/2010/05/30/new-in-kde-partition-manager-1-1-iii- support-for-4096-byte-sectors/ for some background reading, information on how this is going to be improved in the next feature release and links to articles with even more in-depth information on the topic. I'm closing this report as "fixed" because what you describe is not occuring anymore in this same way with the SVN version (i.e. the upcoming 1.1). Regarding the minor bugs you mention: > You can't select and copy the text in Pending Operations or Log Output. You can save the log output in 1.1. > You can undo pending operations (very cool!), but can't redo. File a separate bug report please. > "Recreate existing file system" is poorly named. Yes, I want to keep > what's already there; no, that sounds more destructive. Now > I'm anxious. I don't get your meaning. Recreate _will_ delete data. > There's no "What's This" tooltip help for confusing dialog options > like "Recreate existing file system" and Primary/Extended Partition > type. File a separate bug report please. > I realize units are hard and confusing, but saying "Maximum size: > 3.75 GiB while only allowing me to enter in MiB is not useful. > There's room to instead say "Maximum size: 3835 MiB (3.75 GiB)" The reason for the current behaviour is that the former is always using a "suitable" unit to make the number easily readable (it will use 3.75 TiB if the disk is large enough), but the latter will always use MiB to make data entry easier for the user. I acknowledge this might seem confusing at first. File a separate bug report if you don't like the way it is. > The menu has Help > KDE Partition Manager handbook, but the Kubuntu > package doesn't seem to have this handbook. A packaging problem that you would have to report to Kubuntu. Thanks for responding! I wound up using parted to ensure 1 MiB alignment based on Ted Ts'o blog about SSD 128 kiB block sizes. Your 1.1 Sector alignment feature is exactly what I want in a graphical program.
However, I'm not sure that the 1.1 feature you describe will fix this bug report. The use case is someone naive resizes a partition on some piece of hardware. The weird 38 sector offset of the partition on my SanDisk Cruzer didn't match either the crazy "cylinder" (255 heads?!) alignment or 4k sector alignment. So KDE Partition Manager 1.1 may still move the partition to match the alignment, report this as part of the pending operation, and mystify the user. Some users will want the realignment, some won't.
I would give as much info as possible. As well as the text I suggested for the operation, you could inform the user in the resize dialog:
"Note the partition start does not match the {cylinder|NNNN-byte sector} alignment that {you specified|KDE Partition Manager inferred}."
and give the user the choice (or help them make the change) to move the start or not.
|