From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2smp i686) Description of problem: installer converts ext2 to ext3 befor checking drive space. If there is not enough drive space for the upgrade the upgrade fails and leaves you with a system that will not boot! Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. take RH6.2 system with limited space 2. begin install 3. install converts file system befor checking packages 4. there is not enough room for the upgrade 5. upgrade fails 6. system will not boot! Additional info:
How much space was free initially? Afterwards?
a few hundred megs befor and after because the install never happens. It simply does a conversion then checks to see if there is enough drive space to do the upgrade. When it finds that there is not enough drive space to install the new redhat it lets you know. when you reboot the old kernel has a hartatack when it sees the ext3 file system.
This is related to the fact that the rpmFreeSpace check takes a *really* long time to do. Will revisit for a future release
Current ext2 code is able to mount ext3 without problems as long as the filesystem is cleanly unmounted (and current e2fsprogs can handle the journal replay). Moving things around significantly complicates the logic.