Description of problem: Trying to resize partition that is filled up to 100% Version-Release number of selected component: anaconda-20.25.14-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.14-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 390, in __init__ raise ValueError("new size same as old size") File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1253, in resizeDevice self.devicetree.registerAction(action_class(device, new_size)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 392, in _scheduleActions self.storage.resizeDevice(device, obj.target) ValueError: new size same as old size Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-KDE-x86_64-20-TC5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-300.fc20.x86_64 other involved packages: python-blivet-0.23.8-1.fc20.noarch product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 834260 [details] File: anaconda-tb
Created attachment 834261 [details] File: anaconda.log
Created attachment 834262 [details] File: environ
Created attachment 834263 [details] File: journalctl
Created attachment 834264 [details] File: lsblk_output
Created attachment 834265 [details] File: nmcli_dev_list
Created attachment 834266 [details] File: os_info
Created attachment 834267 [details] File: program.log
Created attachment 834268 [details] File: storage.log
Created attachment 834269 [details] File: ifcfg.log
Proposed as a Blocker for 20-final by Fedora user atorkhov using the blocker tracking app because: Reject or disallow invalid disk and volume configurations without crashing.
I can't reproduce this with F20 TC5 x86_64 Live. I created an ext4 partition covering the whole disk. I used fallocate and dd (to fill the rest) to create files taking up all space. Anaconda doesn't allow me to use the reclaim dialog (the reclaim button is grayed out) and in the custom partitioning when I try to downsize the partition, the size is reverted to original. No crash, behaves as expected. Alexey, you need to be more detailed in the reproduction steps. Thanks.
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted to punt because there is insufficient information available on #1039491 for now, it was not immediately reproducible: delaying decision until wednesday, greenlion will try to come up with a reliable reproducer [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/
(In reply to Kamil Páral from comment #12) > Alexey, you need to be more detailed in the reproduction steps. Thanks. Seems that it enable reclaim button only after free space is enough to install. And also if some correct operation on other partition is involved too. Here are steps I'm using to reproduce: 1. On disk of size 8G create two partitions of size 500M. Fill 100% one of them 2. Start installer, go to reclaim space dialog 3. Press shrink on 100% filled - it won't allow to select size, but changes partition action to "Shrink" 4. Press delete on other one - it will enable reclaim space button.
This criteria seems to be more fitting: Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. It allows shrink operation on 100% filled partition to be requested, so it must be correctly attempted.
It does behave same with any kind of partitions, not only 100% full.
As seems it does matter that tools are used to create partitions, I used fdisk&mkfs.ext4.
Reproducing bug 1039491. I had two partitions, both of them empty (not 100%, not needed). I clicked on Shrink on the first one, but didn't move the slider (that's the point), and clicked on Delete on the second one. Crashed after Reclaim space. Anaconda doesn't take into account that someone might set to shrink a partition, but then not adjust the size at all (and other selected operations allow him to continue and confirm this). cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-20-TC rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.11.10-300.fc20.x86_64 other involved packages: python-blivet-0.23.8-1.fc20.noarch package: anaconda-20.25.14-1.fc20.x86_64 packaging.log: product: Fedora reason: ValueError: new size same as old size release: Fedora release 20 (Heisenbug) version: 20
Reproduced here too. FWIW, this bug is also present in Fedora 19. This is another borderline blocker call for me...I'd like us not to be releasing with this kind of bug, but it depends if we have the will to delay to fix them...guess I'd shade +1, though.
Please try this updates.img: http://vpodzime.fedorapeople.org/f20_blockers_updates.img
(In reply to Vratislav Podzimek from comment #20) > Please try this updates.img: > http://vpodzime.fedorapeople.org/f20_blockers_updates.img it seems that this fixes the bug
Discussed in 2013-12-11 Blocker Review Meeting [1]. Voted as an RejectedBlocker and a AcceptedFreezeException. This is inconvenient, but quite unlikely to hit. It also doesn't present any user data loss. A patch will be considered. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-11/
anaconda-20.25.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.15-1.fc20
Fix verified with a test image built with 20.25.15-1.
anaconda-20.25.15-1.fc20, python-blivet-0.23.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.