Red Hat Bugzilla – Bug 160911
anaconda fails to upgrade with bind mounts in fstab
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
I was upgrading from FC3 to FC4. My current fstab included entries such as:
/dev/hdc1 /mnt/storage1 reiserfs defaults 0 0
/mnt/storage1 /home/files/storage1 none bind 0 0
This fails to mount in the installer because (if I remember correctly), entries from the fstab on the system are mounted under the /mnt/sysimage root, and not /, so /mnt/storage1 would not exist. Anaconda determines from this that it couldn't mount everything it needed to, and forces you to quit and reboot.
My workaround was to boot FC3 again and remove the bind mount entries temporarily, then install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. FC3 system with bind mounts configured in fstab
2. Boot FC4 dvd and try to upgrade.
Actual Results: Anaconda forces the user to exit.
Expected Results: Not sure what the best solution is - in my case, simply not mounting bind mounts in the first place would have sufficed. I'm not sure if this generalizes to others, but there needs to be a way for users with this setup to install.
This works with ext3 partitions. Are you booting with "linux reiserfs"?
No, I didn't boot with "linux reiserfs".
However, it seems unreasonable that I should have to in this scenario -- It was
able to mount my old root partition, which was also reiserfs, to read the fstab
off of it, so I think something else is going on here. If it can mount the old
root there's no reason it shouldn't be able to mount the other partitions as well.
What was the exact error message you got?
This works for me. Can you also provide your /tmp/anacdump.txt file (if you
have one), /tmp/anaconda.log, and the fstab from your installed system?
Those files do not exist on my system. (I actually checked a few days ago and
they weren't there then either, so I guess they just didn't get logged. Sorry
for the long wait.)
Will attach fstab.
Created attachment 115960 [details]
fstab from previous (and current) system
Bind mounts were mounted in rawhide, but the order was incorrect. After a few
test runs, I think I have it working. Changes committed to cvs.