Hi there,
My NFS server is running well for most clients.
But for some client machines, such as, some RHEL5, and a freeBSD, I get 
error as below for some nfs mounts when the system is booting up:

Mount to ...  failed. System Error: no route to host

It's Okay to mount any nfs to directories directly under root (e.g. 
/mtpoint1). The error only occurs for mount points which are subdirectories 
(e.g /opt/mtpoint2).
However, I can manually mount them without any problem when the system has 
booted up. I am sure the nfs entries under /etc/fstab file are Okay becasuse 
I can simply run "# mount /opt/mtpoint2".

Any idea would be appreciated,
Ross 

--Sig_/j0pq1UgwmwjR6xfPJyf6vvq
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 8 Jun 2009 15:47:53 -0400
"Ross" <ross@nospam.ca> wrote:

> Hi there,
> My NFS server is running well for most clients.
> But for some client machines, such as, some RHEL5, and a freeBSD, I get=20
> error as below for some nfs mounts when the system is booting up:
>=20
> Mount to ...  failed. System Error: no route to host

Prehaps network connection isn't negotiated yet at this point, for
example init-script starts pppd which immediately returns while
connection itself takes place in background. Same for the wireless.

Anyway, "no route to host" is an IP-level error, so I'd suggest
triple-check everythong network-related at this point, like plugging
simple ping or tcpdump tests right into the nfs initscript.

> It's Okay to mount any nfs to directories directly under root (e.g.=20
> /mtpoint1). The error only occurs for mount points which are subdirectori=
es=20
> (e.g /opt/mtpoint2).

Now that seems irrational, stroke of luck, prehaps?)

> However, I can manually mount them without any problem when the system ha=
s=20
> booted up. I am sure the nfs entries under /etc/fstab file are Okay becas=
use=20
> I can simply run "# mount /opt/mtpoint2".

That's one more point for "network delay" theory ;)

--=20
Mike Kazantsev // fraggod.net

--Sig_/j0pq1UgwmwjR6xfPJyf6vvq
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkovvpAACgkQASbOZpzyXnHxCgCffL1YrlaiK7G9yFZC7PBC+y0C
FboAoI0OnmKRtUGYXFqQjrUj01h+OgTh
=YCwh
-----END PGP SIGNATURE-----

--Sig_/j0pq1UgwmwjR6xfPJyf6vvq--