From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.1) The problem is that if file is mounted to a directory via the loopback device... the partition that this file and directory reside on cannot be unmounted, hence the install wont complete because there partition remains mounted... Reproducible: Always Steps to Reproduce: For eg.: # mkdir /mnt/dos # make a directory in /mnt # mount -t vfat /dev/sda2 /mnt/dos # mount a dos partition that has the RedHat Cd copied to it # cd /mnt/dos/autoboot # switch to a dir within that partition # mkdir temp # mount the initrd.img that is here # mv initrd.img initrd.gz # gzipd -d initrd.gz # mount initrd temp -o loop (this operation cause /dev/sda2 to go busy forever.. it will now refuse to unmount) # cd temp ... do some stuff in temp ... # cd .. # umount temp # unmount and cleanup # rm -rf temp # cd / # get out of mounted dir # umount /dev/sda2 (or /mnt/dos) (this operation will return an error saying that /dev/sda2 is busy...) The same problem occurs when you mount a file that is on the cdrom during install via loopback and then try to unmount... it makes the cdrom busy.. hence the cdrom wont eject at the completion of RedHat install. Actual Results: if the file mounted as loopback was on cd.. the cd will not eject anymore.. or if it were on a harddisk partition.. that partition will not unmount... Expected Results: partition/cdrom should eject fine because there should not be any thing keeping them busy.
this would be a kernel problem with usage count, perhaps. Not an anaconda bug.
I believe this to be fixed in the errata kernel. Please reopen this bug report if this is not the case.