Hide Forgot
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
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.
I'm sorry but it IS a bug. It should present me with an option to proceed at my own risk.
please, consider reopening of this bug in favour of fixing anaconda (and possibly RPM).
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.
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.