Bug 1252350 - PartitioningError: not enough free space after creating extended partition
Summary: PartitioningError: not enough free space after creating extended partition
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vojtech Trefny
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:3a46fd2a6539df53ed0982a4e17...
: 1340237 1358070 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-11 08:44 UTC by Vojtech Trefny
Modified: 2017-12-12 10:04 UTC (History)
7 users (show)

Fixed In Version: python-blivet-2.1.2-1
Clone Of: 1251688
Environment:
Last Closed: 2017-12-12 10:04:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vojtech Trefny 2015-08-11 08:44:21 UTC
+++ This bug was initially created as a clone of Bug #1251688 +++

Description of problem:
With 3 partitions already on /dev/sda I right-clicked on the free space, chose "add", designated that it should all become an LVM PV, and clicked the button to continue. Got this traceback.

Version-Release number of selected component:
blivet-gui-0.2.8-1.fc22.noarch

Additional info:
reporter:       libreport-2.6.2
blivet-gui.log: 
cmdline:        /usr/bin/python  /bin/blivet-gui
executable:     /bin/blivet-gui
hashmarkername: blivet-gui
kernel:         4.1.2-200.fc22.x86_64
other involved packages: python-blivet-1.0.10-1.fc22.noarch
product:        Fedora
release:        Fedora release 22 (Twenty Two)
type:           Python
version:        22

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/blivetgui/blivetgui.py", line 396, in add_partition
    self._raise_exception(result.exception, result.traceback)
  File "/usr/lib/python2.7/site-packages/blivetgui/blivetgui.py", line 232, in _raise_exception
    raise six.reraise(type(exception), exception, traceback)
  File "/usr/lib/python2.7/site-packages/blivetgui/utils.py", line 928, in add_device
    blivet.partitioning.doPartitioning(self.storage)
  File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 515, in doPartitioning
    allocatePartitions(storage, disks, partitions, free)
  File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 841, in allocatePartitions
    raise PartitioningError(_("not enough free space after "
PartitioningError: not enough free space after creating extended partition

--- Additional comment from Luke Meyer on 2015-08-08 14:00:25 EDT ---



--- Additional comment from Luke Meyer on 2015-08-08 14:00:26 EDT ---



--- Additional comment from Luke Meyer on 2015-08-08 14:00:28 EDT ---



--- Additional comment from Luke Meyer on 2015-08-08 14:00:29 EDT ---



--- Additional comment from Luke Meyer on 2015-08-08 14:00:29 EDT ---



--- Additional comment from Luke Meyer on 2015-08-08 14:00:30 EDT ---

Comment 1 Vojtech Trefny 2015-08-11 08:47:16 UTC
When adding 4th partition (using all remaining available free space on disk) without specifying partType, blivet automatically creates an extended partition, but then fails because there is not enough free space for new logical partition with required size (extended partition use some of available free space).

Comment 2 Vojtech Trefny 2016-05-27 06:43:46 UTC
*** Bug 1340237 has been marked as a duplicate of this bug. ***

Comment 3 Fedora End Of Life 2016-07-19 17:28:11 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Vojtech Trefny 2016-07-20 07:35:27 UTC
*** Bug 1358070 has been marked as a duplicate of this bug. ***

Comment 5 Jan Kurik 2016-07-26 05:11:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 6 Fedora End Of Life 2017-11-16 18:52:12 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 7 Fedora End Of Life 2017-12-12 10:04:51 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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