Bug 162322 - fc4 anaconda install fails to grow lvm if insufficient space
fc4 anaconda install fails to grow lvm if insufficient space
Status: CLOSED DEFERRED
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-02 11:45 EDT by James Hunt
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-08 14:37:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description James Hunt 2005-07-02 11:45:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
I attempted to upgrade an FC3 box to FC4 today, but the install failed since it (correctly) detected that /usr was 65Mb too small for the install to suceed. However, having booted back into FC3, "vgdisplay|grep Free" showed oodles of space left in the Volume Group.

Please could the installer be upgraded to run, "vgdisplay|grep Free", and if space could be made available, offer the user the option of resizing the LV automatically (ie "umount /usr && lvextend -L<some_value> <lv> && e2fsck -f <lv> && resize2fs <lv> && e2fsck -f <lv> && mount /usr")

Of course there is a work around (if you know what you're doing! ;-): boot from the Recovery CD, and use the "lvm" command to do an "lvextend" on /usr. Having done this, the 2nd attempt at the FC4 upgrade worked fine.


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


How reproducible:
Always

Steps to Reproduce:
1. Ensure /usr is almost full on your FC3 box.
2. Ensure that you have lots of spare space in the Volume Group that /usr 
   belongs to.
3. Attempt to upgrade to FC4.


Actual Results:  upgrade popped up a box saying upgrade would not continue (or summut) due to insuffient space.


Expected Results:  The box that pops up stating that 'x' Mb / Gb / etc are required for the install to succeed should provide the option of grabbing the required space from the free pool in the Volume Group (if user is using LVM/LVM2) and if of course there actually *is* sufficient free space in the VG ;-)


Additional info:

I think this change is required since newbies who already have an FC3 system may not relish the idea of hacking around with lvm commands, and could get frustrated. I realize that FC4 comes with system-config-lvm, but of course FC3 doesn't... ;-)

Weirdly, seems that a fresh FC4 system installs system-config-lvm, but an upgrade doesn't....?

If the installer is changed, maybe it would also be wise to explain to the user that this could take a few minutes to complete (if we do the paranoid double e2fsck ;-)
Comment 1 Jeremy Katz 2005-07-08 14:37:13 EDT
Doing this is a part of a bigger effort which would be to add generic partition
resizing.

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