Prior to upgrading to osf/1 v3.0 , we had problems with automount sometimes
not mounting certain areas.
We have nodes 1-7, which hard mount /usr/local from node 8.
These nodes 1-8 then automount a number of remote directories from a single
remote host's partition. An example of the auto.direct on nodes 1-8 is:
/usr/local/src/dir1 -rw,intr remote_node:/export/home/R4D/dir1
/usr/local/src/dir2 -rw,intr remote_node:/export/home/R4D/dir2
.
.
/usr/local/src/dir14 -rw,intr remote_node:/export/home/R4D/dir14
Nodes 1-8 also automounts other remote directories, which always come up when
access is requested, as specified in auto.home. However, the above-mentioned
set of directories never come up after a reboot, when requested, unless you
kill the automounter and restart it.
Any insights, or ways to debug this problem?
Additionally, since the osf/1 v3.0 upgrade, when the automounter refuses to
mount these certain directories, it complains in the following manner and hangs
your process when you try to access them (or any other directories):
NFS2 server node_you_are_on not responding still trying
Why should the node you are sitting on, which exports nothing automounted or
otherwise (node 8 is the only one that exports anything) complain that it
itself is not responding??
Thanks in advance for any ideas, solutions, or directions to go in!!!
Judith Reed
judith_at_npac.syr.edu
systems_at_npac.syr.edu
Received on Tue Feb 07 1995 - 13:20:30 NZDT