Bug 702520

Summary:	anaconda miscalculates disk sizes
Product:	[Fedora] Fedora	Reporter:	Dmitry S. Makovey <dmitry>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-17 18:39:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dmitry S. Makovey 2011-05-06 00:57:08 UTC

Description of problem:
while attempting to install F15 from live media I have created custom partitioning scheme (that I have used for a very long time with RHEL and Fedora deployments prior to F15) and anaconda declined proceeding with install complaining about low disk space


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

Fedora 15 (Beta) KDE LiveCD

How reproducible:

always

Steps to Reproduce:
1. in anaconda create partitioning scheme:
/ - 512M
/usr - 5G
/var - 2G
/var/lib -2G
/tmp - 2G
/boot - 256M

2. hit "next"

  
Actual results:

error message: 

Your / partition is less than 2485.0 MB which is lower than recommended for a normal Fedora Live install.

Expected results:

normal install

Comment 1 Brian Lane 2011-05-06 02:59:48 UTC

Well, your / is 512M which is < 2485M. Yes, you are going to mount a number of other partitions but Anaconda really doesn't know how the packages are going to distribute their files.

Comment 2 Dmitry S. Makovey 2011-05-06 14:25:13 UTC

I'm sorry but it IS a bug. It should present me with an option to proceed at my own risk.

Comment 3 Dmitry S. Makovey 2011-05-06 14:28:05 UTC

please, consider reopening of this bug in favour of fixing anaconda (and possibly RPM).

Comment 4 Dmitry S. Makovey 2011-05-06 15:18:55 UTC

Here's my F14 setup:

[root@dimon2 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_dimon2-rootfs
                      724M  474M  215M  69% /
tmpfs                 1.9G  2.0M  1.9G   1% /dev/shm
/dev/sda1             485M   61M  399M  14% /boot
/dev/mapper/luks-8a7881d2-b4dc-4d4c-9bd9-548c1e5c6acb
                      4.0G  2.9G  900M  77% /home
/dev/mapper/vg_dimon2-optfs
                     1008M  168M  789M  18% /opt
/dev/mapper/vg_dimon2-optfs
                     1008M  168M  789M  18% /srv
none                  1.9G  101M  1.8G   6% /tmp
/dev/mapper/vg_dimon2-usrfs
                      7.9G  5.7G  1.9G  76% /usr
/dev/mapper/vg_dimon2-varfs
                     1008M  473M  485M  50% /var
/dev/mapper/vg_dimon2-varlogfs
                      2.0G  136M  1.8G   8% /var/log
/dev/mapper/vg_dimon2-varlibfs
                      6.0G  2.9G  2.9G  50% /var/lib

I believe last time I may have had to resort to crafting a kickstart file, but I don't see why kickstart and GUI install should (can?) have different constraints and why GUI install can't let me proceed when I *know* there is enough space for install.

Comment 5 Chris Lumens 2011-05-17 18:39:37 UTC

The follow up to adding a warning allowing you to continue at your own risk is that someone will file a bug saying they continued at their own risk and it crapped out anyway, so anaconda should handle that too.  We've seen this sort of thing over and over again.  Sorry.  Comment #1 still applies.