asked on no NFS mounts at boot up
i have just "upgraded" a box from open suse 10.2 to 10.3. prior to upgrade the box would happily mount NFS filesystems on boot-up..... but now it doesn't and i have to manually mount them subsequently. i've tried trawling the suse support DB without success... anybody any suggestions/ideas!?
thanks
roger
thanks
roger
LinuxLinux Distributions
Last Comment
shallxrg
Once the system is up, does "mount -a" mount the NFS partitions? Look at /etc/fstab if not.
ASKER
yes... i immediately use 'mount -a' and it works without complaint or hesitation(!)... i hadn't made any changes either to 'fstab' on the client m/c or to the exports at the remote m/c.... is it possible that the NFS client is not fully 'started' at the time 'fstab' is being scanned(?!)... i'm wondering if it is easy to test that theory(?)
Are you using autofs (automount)?
If not, have a look at:
Is the portmap daemon starting at boot?
Do you have a firewall up, does it block 111/tcp/udp & the other RPC ports (rpcinfo -p <host>)?
To check that the client can "see" the server's NFS exports using "showmount -e <host>"
If you're mounting through fstab, look in there to make sure that the file is not corrupted in someway, or you have weird/incorrect mount points/options.
Have you checked /var/log/messages, /var/log/boot.* & dmesg for any errors?
If not, have a look at:
Is the portmap daemon starting at boot?
Do you have a firewall up, does it block 111/tcp/udp & the other RPC ports (rpcinfo -p <host>)?
To check that the client can "see" the server's NFS exports using "showmount -e <host>"
If you're mounting through fstab, look in there to make sure that the file is not corrupted in someway, or you have weird/incorrect mount points/options.
Have you checked /var/log/messages, /var/log/boot.* & dmesg for any errors?
The fact that mount -a works fine after boot is complete does seem to indicate some services are being started in the "wrong" order - certainly a different order from previously.
Does SuSe have regular System V init with /etc/rc.d/rc.<n> directories stuffed full of symbolic links with names starting S<n><n> or K<n><n>?
If it does, the order of starting stuff is governed by the S<n><n> links in rc.<runlevel>. Have a look and see if that makes sense.
If you have a backup of /etc/rc.d from SuSe 10.2, you could restore that somewhere and compare link names to see what has changed.
On an old Fedora distribution I have, the network mounts were done by S25netfs, i.e. after S05kudzu S08iptables S09isdn S10network S12syslog S13portmap S14nfslock S18rpcgssd S19rpcidmapd S19rpcsvcgssd S20random S24pcmcia
Does SuSe have regular System V init with /etc/rc.d/rc.<n> directories stuffed full of symbolic links with names starting S<n><n> or K<n><n>?
If it does, the order of starting stuff is governed by the S<n><n> links in rc.<runlevel>. Have a look and see if that makes sense.
If you have a backup of /etc/rc.d from SuSe 10.2, you could restore that somewhere and compare link names to see what has changed.
On an old Fedora distribution I have, the network mounts were done by S25netfs, i.e. after S05kudzu S08iptables S09isdn S10network S12syslog S13portmap S14nfslock S18rpcgssd S19rpcidmapd S19rpcsvcgssd S20random S24pcmcia
ASKER
not using autofs; portmapper running ok; no intermediate firewall; showmount -e ok; fstab ok (has to be, since 'mount -a' works);nothing relevant in 'messages'; 'boot.log' has "mounting local filesystems" but does not refer to NFS mounts
ASKER
thanks duncan... i'll examine the startup scripts later today... i know suse has a similar (though not identical) setup... maybe a judicious 'sleep' will help...
cheers
roger
cheers
roger
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ok... i have established that the 'nfs' startup script differs significantly between 10.2 and 10.3... very suspicious!! ... i shall need to insert some trace to try and see what it's (not) doing... this may take some time to fit in, but i'll report back when i have some findings
cheers
roger
cheers
roger
ASKER
thanks duncan... i was looking for something more complex... i've posted a comment to describe the precise fix ... cheers roger
ASKER
ok... many thanks to duncan_roe... it turns out that the symbolic links to 'nfs' in /etc/init.d/rc*.d/ were not in place... to 'manufacture' them i went into YasT... NFS Client... (which then correctly displayed the relevant content of my 'fstab') and then clicked 'finish' ... bingo! ... i suppose the root of the problem lay in the fact that i had not used 'YasT' to construct the fstab entries.... had i done so it wouldn't have happened!.... "a sadder and a wiser man, he rose the morrow morn"(!)