Red Hat Bugzilla – Bug 443736
nfs mounting fails forever once it failed
Last modified: 2008-06-21 16:00:20 EDT
Description of problem:
Once mistakenly specifying non-existent directory with nfs mounting, even if
correct directory is given, the install process can't go forward.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.specify non-existent directory with nfs install and see "That directory could
not be mounted from the server" error.
2.specify a directory that exactly has Fedora image.
should go forward next step
From the log:
Running... /bin/mount -n -t iso9660 -o ro /dev/sr0 /mnt/stage2
mount: /dev/sr0 already mounted or /mnt/stage2 busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/stage2
Running... /bin/mount -n -t nfs -o nolock nfserver:/mnt/path/to/Fedora/i386/os
mount.nfs: /mnt/source is busy or already mounted
This should be fixed in the next build of anaconda, I think. Judging from your
log file blurb I assume you are booting off the boot.iso. This is likely just a
side effect of never unmounting the CD when given a bad NFS directory and not
doing the proper cleanup when we go around for another try.
Oops, sorry. yes, you're right. I have tried with boot.iso.
Thank you for fixing!
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here: