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. The only thing I can see in /var/log/messages that seems like it might have any relevance is a warning that the powersave-set_disk_settings could not retrieve a list of disks from the HAL. But that seems to be a bit of a stretch for impacting an NFS mount. There is one difference between the file systems, on janus /proddb is owned by the mysql user so that it appears owned by mysql on damocles (I intend to put the mysql DB on this mount). Could this be somehow preventing it from mounting automatically? Any help is appreciated. Tim Donnelly Systems/Network Administrator Colorado Alliance of Research Libraries (303)759-3399 x106 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tim Donnelly wrote:
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. YMMV -- HTH Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
participants (2)
-
Philippe Andersson -
Tim Donnelly