Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1027947 +++
Description of problem:
I had old LVM partition scheme on my disk. I have resized old root partition to some big number (130 GB on my 20 GB disk), accepted changes (ran without problem), and then tried to resize it back to old value and this showed up.
Version-Release number of selected component:
anaconda-20.25.6-1
The following was filed automatically by anaconda:
anaconda 20.25.6-1 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 581, in __init__
raise ValueError("new size same as old size")
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1250, in resizeDevice
self.devicetree.registerAction(action_class(device, new_size))
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1454, in _save_right_side
self.__storage.resizeDevice(device, size)
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2802, in on_apply_clicked
self._save_right_side(self._current_selector)
ValueError: new size same as old size
Additional info:
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Beta\x20i386 rd.live.check quiet BOOT_IMAGE=vmlinuz
executable: /sbin/anaconda
hashmarkername: anaconda
kernel: 3.11.6-301.fc20.i686
product: Fedora
release: Cannot get release name.
type: anaconda
version: 20-Beta
Potential duplicate: bug 868698
--- Additional comment from Jan Sedlák on 2013-11-07 08:54:20 EST ---
Steps to reproduce:
1. Install Fedora using default LVM partition scheme.
2. Boot F20 anaconda installer.
3. Choose custom partitioning.
4. Resize existing root partition to bigger size than your disk have (130 GB) and click "update settings". It shows that root will have 130 GB.
5. Resize your root partition back to old size.
Reproduced with anaconda-19.31.42-1.el7, verified with anaconda-19.31.56-1.el7.
Anaconda doesn't allow LV sizes bigger than VG size.
Moving to VERIFIED.
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.