Red Hat Bugzilla – Bug 389401
cannot get nfs shares to mount on boot
Last modified: 2014-03-16 23:11:33 EDT
adding mount commands to the /etc/fstab do not run and therefore won't mount my nfs shares on boot. also adding mount commands to /etc/rc.d/rc.local do not run and therefore won't mount nfs shares on boot How reproducible: Added these commands to fstab: 192.168.1.102:/mnt/sdc1 /mnt/fileserver nfs defaults 0 0 192.168.1.102:/mnt/sdb1 /mnt/fileserver2 nfs defaults 0 0 added these to rc.local /bin/mount -t nfs 192.168.1.102:/mnt/sdc1 /mnt/fileserver /bin/mount -t nfs 192.168.1.102:/mnt/sdb1 /mnt/fileserver2 Actual results: The mounts do not accur during boot with either of the above methods Expected results: nfs shares should be mountable during the boot sequence
In what way do they not mount? Is rpcbind and nfslock started?
rpcbind and nfslock are both running. They don't mount after bootup. Not sure there are more ways to describe. They are either mounted or unmounted.
Does 'mount -a -t nfs' work?
Yes. Running the mount command from command prompt after bootup works fine. Also, if i put the mount commands in the rc.local, i can run the rc.local file from the command prompt (/etc/rc.d/./rc.local) and it work fine. So the issue is on bootup only. Is this perhaps a problem due to me starting with Fedora 8 RC3 and then upgrading to the final? Some startup script file out of wack? I'm at a loss here.
Any SELinux errors in /var/log/audit/audit.log, or dmesg?
I've done a test here; adding an entry in fstab seems to work OK - it's mounted correctly by netfs.
SELinux is off.
Explicitly add the options bg,hard,intr to your fstab line. Hard will force it to keep retrying until it mounts. Bg will allow mount to go on while it keeps trying in the bg. Not the best fix, but it should allow it to automount the instant your boot process is done enough to let it. Check any iptables scripts that might be blocking the ports until the boot is done. Also, if you want some fun, migrate to NFSv4 and tcp. BTW, works fine for me on F8.
Resolved: see this bug report for resolution. https://bugzilla.redhat.com/show_bug.cgi?id=427157
*** This bug has been marked as a duplicate of 427157 ***