Using OpenSUSE 11.4 on a backup server. At boot, it needs to connect to the main server’s NFS share. Watching the text scroll up the screen, it’s obvious that the system waits for anything up to several minutes showing ‘mounting NFS…’. Once it (eventually) passes that point, the rest of the boot procedure is as fast as expected.
If NFS is disabled at boot, normal boot times are restored.
If the NFS client is restarted via ‘rcnfs restart’ once the system is up and running, it’s instant.
If NFS is disabled at boot and started manually afterwards, it start instantly.
Once running, NFS behaves normally.
The backup server has two ethernet ports, connected via a switch to the main server, which also has two ethernet ports.
All ports are configured via DHCP from a router, with all addresses reserved on the router so that all important devices are kept at the same locations.
Any thoughts?
On 2011-05-11 21:06, speakeasy wrote:
> All ports are configured via DHCP from a router, with all addresses
> reserved on the router so that all important devices are kept at the
> same locations.
Why then not use fixed IPs directly? No delay asking for a lease.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
speakeasy wrote:
> Using OpenSUSE 11.4 on a backup server. At boot, it needs to connect to
> the main server’s NFS share. Watching the text scroll up the screen,
> it’s obvious that the system waits for anything up to several minutes
> showing ‘mounting NFS…’. Once it (eventually) passes that point, the
> rest of the boot procedure is as fast as expected.
A few random questions and ideas:
What OS is running on the main server?
My first thought is that there’s an NFS version conflict. My solution
has been to disable NFV V4 on recent releases so everything coexists
happily with V3
Also, what is in dmesg and/or /var/log/messages?
If you take the mount out of the boot sequence (add noauto to
/etc/fstab?), what is shown when you subsequently mount it manually with
the -v option?