Bug 1029633 - Re-using LVM partitions makes them non-resizable in certain cases
Summary: Re-using LVM partitions makes them non-resizable in certain cases
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.0
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1027714
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 19:18 UTC by David Lehman
Modified: 2021-09-03 14:08 UTC (History)
6 users (show)

Fixed In Version: python-blivet-0.18.15-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1027714
Environment:
Last Closed: 2014-06-13 09:33:16 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Lehman 2013-11-12 19:18:45 UTC 
+++ This bug was initially created as a clone of Bug #1027714 +++

Description of problem:
I had a previous F20 LVM installation. I wanted to reuse swap, /boot and /, and delete /home. I achieved that, but I could not enlarge / to occupy space reclaimed by deleting /home. Anaconda claims that the partition is not resizable.

Please see the video.

Also please notice that the free space counter is totally off, not reflecting deleted partitions.

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

How reproducible:
always

Steps to Reproduce:
1. create /boot as a standard partition and swap, / and /home on LVM
2. install, then reboot again into the installer
3. reuse swap and /boot
4. delete /home
5. try to reuse / and enlarge it to occupy space reclaimed by deleting /home
6. see that the partition refuses to be enlarged
Comment 2 Michal Kovarik 2014-02-11 15:05:52 UTC 
Verified on RHEL-7.0-20140210.0 with python-blivet-0.18.23-1.el7. It's possible enlarge '/' mountpoint.
Comment 3 Ludek Smid 2014-06-13 09:33:16 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.