Bug 715125 - fdisk d command of a range of partitions is not supported, but executed badly rather than rejected
Summary: fdisk d command of a range of partitions is not supported, but executed badly...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: util-linux
Version: 15
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 22:28 UTC by Ken Fuchs
Modified: 2012-08-07 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Fedora 15 on Tunnel Creek SOC and Top Cliff chipset.
Last Closed: 2012-08-07 16:46:31 UTC
Type: ---


Attachments (Terms of Use)
This text attachment contains a shell log illustrating an example of this bug. (2.92 KB, text/plain)
2011-06-22 14:33 UTC, Ken Fuchs
no flags Details

Description Ken Fuchs 2011-06-21 22:28:29 UTC
Description of problem:

Using fdisk, attempted to delete a sequence of partitions by giving a range of partitions (n-m) to the d command rather than giving them one at a time, repeating the d command as needed.  What fdisk did was delete the first partition and decremented the partition number of all subsequent partitions, such that each partition <n> became partition <n-1>.  Surprisingly different from the expected result, deleting partitions n-m.  Surprises from fdisk is "not a good thing". (TM)

Version-Release number of selected component (if applicable):

2.19.1-1.fc15

How reproducible:

While using fdisk, enter the d (delete) command and enter a range of partitions similar in construction to the range of deletable partition numbers.

Steps to Reproduce:
1. fdisk /dev/fdisk
2. p
3. d
4. 5-17
5. p
6. q
  
Actual results:

Partition 5 was deleted.  Partitions 6-17 were decremented to partitions 5-16 respectively.

The attached text file shows the input and output of an fdisk invocation that illustrates the partition deletion issue being reported.

Expected results:

Either report "5-17" as an invalid partition number or delete partitions 5-17.

Additional info:

With mounting via UUID, renumbering partitions isn't as disastrous as it would be when mounting by partition number, but some people still mount via the raw special block devices, even on Fedora.

Comment 1 Ken Fuchs 2011-06-22 14:33:16 UTC
Created attachment 506021 [details]
This text attachment contains a shell log illustrating an example of this bug.

At bug creation, a text file failed attachment.  Attempting to attach the file again.

Comment 2 Fedora End Of Life 2012-08-07 16:46:33 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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