Bug 16710 - fdisk prompt: "+sectors" should read "+blocks" or +N should allocate sectors, not blocks
Summary: fdisk prompt: "+sectors" should read "+blocks" or +N should allocate sectors,...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-06 04:26 CEST by Pierre Fortin
Modified: 2018-04-14 15:09 CEST (History)
2 users (show)

See Also:
Source RPM: util-linux
CVE:
Status comment:


Attachments

Description Pierre Fortin 2015-09-06 04:26:58 CEST
Description of problem: Creating new partition table, user is prompted with:
"Last sector, +sectors or +size{K,M,G} (<lo>-<hi>, default <hi>): "
Entering +<number> results in <number> BLOCKS, not sectors being added.


Version-Release number of selected component (if applicable):  2.25.2-3.mga5


How reproducible: always


Steps to Reproduce:
1. fdisk /dev/sdx
2. create an extended partition
3. create a logical partition from <lo> to +<number>

Created partition is now <number> BLOCKS in size.


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-09-06 09:16:50 CEST
util-linux-2.25.2-3.1.mga5 is in updates_testing

I doubt this got fixed, but you might want to try, anyway

CC: (none) => luigiwalser, marja11
Assignee: bugsquad => tmb

Comment 2 David Walser 2015-09-06 16:05:54 CEST
Find the upstream commit that fixes it and we'll include it.
Comment 3 Marja Van Waes 2018-04-14 12:21:55 CEST
@ Pierre,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja
Comment 4 Pierre Fortin 2018-04-14 15:09:58 CEST
Operating correctly in mga6.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.