Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41632 - [util-linux] fdisk interactive 'v' usage does not always work

Attached to Project: Arch Linux
Opened by Robert Bowers (onedingo) - Wednesday, 20 August 2014, 08:30 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 21 August 2014, 11:25 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When using fdisk (util-linux 2.25-3) interactively, pressing v does not always show unallocated sectors. My computer has 3 dos partitioned drives, all of which are in use.

*Be careful doing this*

# fdisk /dev/sda

Welcome to fdisk (util-linux 2.25).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): v
Remaining 7538032 unallocated 512-byte sectors.

Command (m for help): q

# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.25).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): v

Command (m for help): q

#

/dev/sdc behaves as /dev/sdb
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 21 August 2014, 11:25 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Upstream asserts this is WAI.
Comment by Robert Bowers (onedingo) - Wednesday, 20 August 2014, 08:50 GMT
This may help:

# truncate -s 16M bin
# losetup -f bin
(use this to find where it looped)
# losetup -a
/dev/loop0: [65024]:292804 (/root/bin)
# fdisk /dev/loop0

Welcome to fdisk (util-linux 2.25).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x7235e130.

Command (m for help): v
Remaining 32767 unallocated 512-byte sectors.

Command (m for help): n

(now just accept all the defaults)

Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p):

Using default response p.
Partition number (1-4, default 1):
First sector (2048-32767, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-32767, default 32767):

Created a new partition 1 of type 'Linux' and of size 15 MiB.

Command (m for help): v

Command (m for help):

---

It used to print
Remaining 2047 unallocated 512-byte sectors.
for a layout like this but now prints nothing.
Comment by Dave Reisner (falconindy) - Wednesday, 20 August 2014, 12:25 GMT
There's been a huge number of changes to the fdisk code since the last release. Could you report this upstream?
Comment by Robert Bowers (onedingo) - Wednesday, 20 August 2014, 19:16 GMT
I just sent a copy to the mailing list at http://vger.kernel.org/vger-lists.html#util-linux , so it should show in the archives at some point.

Loading...