Bug 1222811 - ValueError: requested size 3 GiB must fall between minimum size 6.59 GiB and maximum size 16 TiB
Summary: ValueError: requested size 3 GiB must fall between minimum size 6.59 GiB and ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d7f3f4d1f2a3353352ba74e8095...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-19 08:39 UTC by Petr Schindler
Modified: 2016-07-19 14:09 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 14:09:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (576.53 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: anaconda.log (20.50 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: environ (614 bytes, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: journalctl (244.17 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: lsblk_output (2.29 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: nmcli_dev_list (1.20 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: os_info (496 bytes, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: program.log (55.82 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: storage.log (158.32 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details
File: ifcfg.log (2.26 KB, text/plain)
2015-05-19 08:39 UTC, Petr Schindler
no flags Details

Description Petr Schindler 2015-05-19 08:39:21 UTC
Description of problem:
I run F22-Live-Workstation TC4 on virtual machine. In custom partitioning I chose existing lvm and tried to change its size to 3 GiB (from about 8.5 GiB). It crashed after I clicked on update settings

Version-Release number of selected component:
anaconda-core-22.20.12-1.fc22.x86_64

The following was filed automatically by anaconda:
anaconda 22.20.12-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 204, in _setTargetSize
    raise ValueError("requested size %s must fall between minimum size %s and maximum size %s" % (newsize, self.minSize, self.maxSize))
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 758, in apply
    self.device.format.targetSize = self._targetSize
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 493, in registerAction
    action.apply()
  File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 1173, in resizeDevice
    self.devicetree.registerAction(action_class(device, new_size))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 779, in _handle_size_change
    self._storage_playground.resizeDevice(use_dev, use_size)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 129, in decorated
    return func(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1187, in _save_right_side
    self._handle_size_change(size, old_size, device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2643, in on_update_settings_clicked
    self._save_right_side(self._current_selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 242, in _run_once_one_arg
    self._func(*args, **kwargs)
ValueError: requested size 3 GiB must fall between minimum size 6.59 GiB and maximum size 16 TiB

Additional info:
cmdline:        /usr/bin/python2  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-T4 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.0.2-300.fc22.x86_64
other involved packages: anaconda-gui-22.20.12-1.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch
product:        Fedora
release:        Fedora release 22 (Twenty Two)
type:           anaconda
version:        22

Comment 1 Petr Schindler 2015-05-19 08:39:26 UTC
Created attachment 1027027 [details]
File: anaconda-tb

Comment 2 Petr Schindler 2015-05-19 08:39:29 UTC
Created attachment 1027028 [details]
File: anaconda.log

Comment 3 Petr Schindler 2015-05-19 08:39:30 UTC
Created attachment 1027029 [details]
File: environ

Comment 4 Petr Schindler 2015-05-19 08:39:34 UTC
Created attachment 1027030 [details]
File: journalctl

Comment 5 Petr Schindler 2015-05-19 08:39:35 UTC
Created attachment 1027031 [details]
File: lsblk_output

Comment 6 Petr Schindler 2015-05-19 08:39:37 UTC
Created attachment 1027032 [details]
File: nmcli_dev_list

Comment 7 Petr Schindler 2015-05-19 08:39:39 UTC
Created attachment 1027033 [details]
File: os_info

Comment 8 Petr Schindler 2015-05-19 08:39:41 UTC
Created attachment 1027034 [details]
File: program.log

Comment 9 Petr Schindler 2015-05-19 08:39:44 UTC
Created attachment 1027035 [details]
File: storage.log

Comment 10 Petr Schindler 2015-05-19 08:39:46 UTC
Created attachment 1027036 [details]
File: ifcfg.log

Comment 11 Kamil Páral 2015-05-19 09:38:37 UTC
Another user experienced a similar problem:

Trying to reproduce bug 1040413. Crashed at step 5. It seems it happens when you enter a lower size than is the minimum size of the filesystem on that LV.

addons:         com_redhat_kdump
cmdline:        /usr/bin/python2  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22_T4-x86_64 quiet
dnf.rpm.log:    May 19 09:27:37 INFO --- logging initialized ---
hashmarkername: anaconda
kernel:         4.0.2-300.fc22.x86_64
package:        anaconda-22.20.12-1
product:        Fedora
reason:         ValueError: requested size 5.47 GiB must fall between minimum size 6.17 GiB and maximum size 16 TiB
release:        Cannot get release name.
version:        22

Comment 12 Kamil Páral 2015-05-19 10:19:10 UTC
Yes, this happens when you input a lower value than minimum filesystem size (unless you choose to reformat the volume).

It seems to be fixed with inst.updates=https://dlehman.fedorapeople.org/updates/updates-1211746.0.img from bug 1211746 comment 21.

Comment 13 Kamil Páral 2015-05-21 12:12:11 UTC
This is fixed in RC2.

Comment 14 Amadeus W.M. 2015-06-06 21:55:03 UTC
Another user experienced a similar problem:

Installing F22 to disk from live workstation dvd, during manual disk partitioning. 
I have my own partition scheme with various data partitions so I always partition manually.
 
My old F20 /boot partition was 200Mb and I wanted to make it 300Mb in F22. The error message occured twice in a row when I click update settings, after changing the /boot partition size from 200 (in F20) to 300 (in F22).


cmdline:        /usr/bin/python2  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-3 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 
hashmarkername: anaconda
kernel:         4.0.4-301.fc22.x86_64
other involved packages: anaconda-gui-22.20.13-1.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch
package:        anaconda-core-22.20.13-1.fc22.x86_64
packaging.log:  
product:        Fedora
reason:         ValueError: requested size 199.19 MiB must fall between minimum size 200 MiB and maximum size 16 TiB
release:        Fedora release 22 (Twenty Two)
version:        22

Comment 15 Kamil Páral 2015-06-08 11:12:42 UTC
Well, it seems it is not fixed. Amadeus, if you perhaps see it again, please save /tmp/anaconda-tb-* file and attach it here. Thanks.

Comment 16 Fedora End Of Life 2016-07-19 14:09:41 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.


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