RE: [SLE] nfs fails to mount at boot
![](https://seccdn.libravatar.org/avatar/c64c2eacb8f713e5e3fd051c8a060920.jpg?s=120&d=mm&r=g)
Hi,
From: Eddie [mailto:eddie.howson@dsl.pipex.com] Hi all,
I've noticed that none of my nfs directories mount at bootup despite being set as auto in the /etc/fstab file. Issuing the "mount -a" command as root mounts them immediately without any problems.
Does anyone know why they fail to mount initially? Would be grateful for any advice, tips or ideas.
/etc/fstab is used before the runlevel starts. So the network is not configured yet and nfs will fail.
TIA
Eddie
cheers, Stefan PS: You can create your own rc-script mounting the desired filesystems. Then copy it to /etc/init.d and use insserv and chkconfig (or the runlevel editor of yast) to enable the service.
![](https://seccdn.libravatar.org/avatar/d08ade365636ca76c6f2cd1499a207f0.jpg?s=120&d=mm&r=g)
I have experience this also. Correct on the order. I also found in /etc/init.d/nfs a command to run "ldconfig" after mounting the nfs/directory. This seemed to make a nfs bootup much slower. We only use nfs as a backup storage and have no useable libs to it. Yesterday playing at a place with DHCP which changed all of the IP# at boot time NFS hung and caused the process to lockup. I unplugged the RJ45 connector and tried again. That worked! A fellow suggested a fix to the DHCP issue form his FreeBSD knowledge base. I missed grasping it, but it did deal with adding "alias" to the nfs ifconfig information. Peer Stefan wrote:
Hi,
From: Eddie [mailto:eddie.howson@dsl.pipex.com] Hi all,
I've noticed that none of my nfs directories mount at bootup despite being set as auto in the /etc/fstab file. Issuing the "mount -a" command as root mounts them immediately without any problems.
Does anyone know why they fail to mount initially? Would be grateful for any advice, tips or ideas.
/etc/fstab is used before the runlevel starts. So the network is not configured yet and nfs will fail.
TIA
Eddie cheers, Stefan PS: You can create your own rc-script mounting the desired filesystems. Then copy it to /etc/init.d and use insserv and chkconfig (or the runlevel editor of yast) to enable the service.
-- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.net
![](https://seccdn.libravatar.org/avatar/63cf57a3adf2a94a6114d0921bd2ad37.jpg?s=120&d=mm&r=g)
On Thursday 03 July 2003 11:23, Peer Stefan wrote:
I've noticed that none of my nfs directories mount at bootup despite being set as auto in the /etc/fstab file. Issuing the "mount -a" command as root mounts them immediately without any problems.
/etc/fstab is used before the runlevel starts. So the network is not configured yet and nfs will fail.
When did that stop working? I'm still on SuSE 8.1 and the nfs directories that I set as auto (more precisely: I did not set them "noauto") in the /etc/fstab are being mounted perfectly... (and I had those settings since 7.0, it always worked) Hansen -- Powered by SuSE 8.1pro - KDE 3.0.3 - KMail 1.4.3
participants (3)
-
Donn Washburn
-
Johannes Liedtke
-
Peer Stefan