I tried Philippe's soulution and got no joy.

To test the theory that it was a name resolution problem, I inserted a third 
mount into the fstab file.  I placed this before /proddb and /prodobj.  The 
first filesystem failed to mount, but the second and third worked as one would 
expect.  I also changed the fstab entry for the first filesystem to point to 
the IP address instead of the hostname.  No luck.

In looking at the nfs start up script in /etc/init.d I noticed a comment about 
it sometimes being helpful to mount NFS devices in the backgroup with an & and 
a sleep time.  I modified the startup script as mentioned, but still the first 
mount is "ignored" while subsequent mounts work fine.

Google is not helping, does anyone else have any ideas?

Thanks

> My problem:
> 
> I have a server (damocles running Suse 10) that is supposed to be
> mounting two remote file systems via NFS. Both remote file systems
> are being served by the same server (janus running SLES 9). The
> relevant portions of the fstab file for damocles looks like this:
> 
> janus.coalliance.org:/proddb /proddb nfs defaults 0 0 
> janus.coalliance.org:/prodobj /prodobj nfs defaults 0 0
> 
> Both systems are being served with the same options from janus.
> 
> When damocles is booted, /prodobj mounts fine, but /proddb will not
> mount. If I run mount -a from the command line it mounts like it
> should.
I've seen the exact same behaviour on a SLES9 server here that mounts
NFS filesystems exported by an HP-UX server.

In our case at least, the problem seemed to be caused by a name
resolution issue: either the NFS mount request doesn't wait long enough
for an answer, or the resolver isn't fully operational yet when the
first mount request kicks in. By the time the second mount request is
reached, name resolution works fine (likewise for all subsequent requests).

I fixed it by adding the server name and IP address in the /etc/hosts
file on the NFS client. In you case:

w.x.y.z janus janus.coalliance.org

I know it's not ideal, but it worked for us.


--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to