Red Hat Bugzilla – Bug 1008633
ValueError: invalid target size request
Last modified: 2013-11-13 04:20:05 EST
Description of problem:
Guest has W7 default install.
I tried to resize the big ntfs partition in custom partitioning.
I changed the size and then clicked 'update parameters'.
Anaconda crashed immediately.
Version-Release number of selected component:
The following was filed automatically by anaconda:
anaconda 20.15-1 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 207, in _setTargetSize
raise ValueError("invalid target size request")
File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 589, in __init__
self.device.format.targetSize = newsize
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1247, in resizeDevice
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1441, in _save_right_side
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2788, in on_apply_clicked
ValueError: invalid target size request
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 quiet BOOT_IMAGE=vmlinuz
release: Cannot get release name.
Potential duplicate: bug 986575
Created attachment 798369 [details]
Created attachment 798370 [details]
Created attachment 798371 [details]
Created attachment 798372 [details]
Created attachment 798373 [details]
Created attachment 798374 [details]
Created attachment 798375 [details]
Created attachment 798376 [details]
Created attachment 798377 [details]
Created attachment 798378 [details]
Created attachment 798379 [details]
I used manual partitioning, selected an existing partition and wanted to adjust its size. Instead of providing "2 GB" value into the Size field, I used just "2" (no unit). Anaconda crashed after I pressed Update Settings.
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-20-Be rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0
other involved packages: python-blivet-0.23.1-1.fc20.noarch
reason: ValueError: invalid target size request
release: Fedora release 20 (Heisenbug)
Proposing Beta blocker:
"When using the custom partitioning flow, the installer must be able to: Reject or disallow invalid disk and volume configurations without crashing. "
Discussed at 2013-10-23 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-23/f20-blocker-review.2013-10-23-16.00.log.txt . Accepted as a blocker per criterion cited in comment #13.
Works for me.
Per c12: test Fedora 20 Beta TC6 with existing Windows7 taking up the entire (qcow2) disk. Clicked on primary partition 2, NTFS, clicked on Desired Capacity and entered in 2 without units and clicked on Update Settings. No crash, Desired Capacity resets to 12.163GB. Click partition "create automatically" link, partitions created. Installs fine. Boots Fedora and Windows as expected.
20.25.4-1 went stable as part of FEDORA-2013-20033, and the fix was verified, so this can be closed.
I reproduced this again with 20.25.6-1 (Fedora 20 Beta RC5). I resized existing logical volume to 100GB and it didn't fail although the disk is only 20GB. Then I resized it again to 100TB and it crashed with attached tb.
Created attachment 821148 [details]
Discussed in the 2013-11-07 Go/No-Go meeting . Voted as a RejectedBlocker. While unfortunate, resize issues are not covered in the F20 beta release criteria. Thus, this bug is rejected as a release blocking issue for F20 beta. Please re-propose as a F20 final blocker and mark for inclusion in CommonBugs.
(In reply to Martin Krizek from comment #17)
> I reproduced this again with 20.25.6-1 (Fedora 20 Beta RC5). I resized
> existing logical volume to 100GB and it didn't fail although the disk is
> only 20GB. Then I resized it again to 100TB and it crashed with attached tb.
This is a separate bug. Please open a new report for it and include your logs. Thanks.
Correct blocker status (rejected, not accepted).
Per c#20 this should be closed, yes?
Martin, can you please create a new bug as dlehman requested?
I have already done it: bug 1028367