[NFS] NFS clients behind a masqueraded gateway
rok at ucsd.edu
Fri Apr 26 09:36:15 PDT 2002
you're probably hitting NAT timeouts and NFS clients don't handle this
well. We have the same setup on our cluster but we are using automountd on
our NFS mounted directories - which works nicely around this problem.
On Thu, Apr 25, 2002 at 09:02:44PM +0200, Steffen Persvold wrote:
> Hi Wulfers,
> I'm taking the liberty to post my question here as well since it might be
> relevant for some of you and you might have some experience with this.
> I've also posted the mail to the NFS mailing list, but I haven't gotten
> any answers (yet).
> Any pointers to what the problem might be are higly appreciated.
> On Thu, 18 Apr 2002, Steffen Persvold wrote:
> > Hi all,
> > I'm experiencing some problems with a cluster setup. The cluster is set up
> > in a way that you have a frontend machine configured as a masquerading
> > gateway and all the compute nodes behind it on a private network (i.e the
> > frontend has two network interfaces). User home directories and also other
> > data directories which should be available to the cluster (i.e statically
> > mounted in the same location on both frontend and nodes) are located on
> > external NFS servers (IRIX and Linux servers). This seems to work fine
> > when the cluster is in use, but if the cluster is idle for some time (e.g
> > over night), the NFS directories has become unavailable and trying to
> > reboot the frontend results in a complete hang when it tries to unmount
> > the NFS directories (it hangs in a fuser command). The frontend and all
> > the nodes are running RedHat 7.2, but with a stock 2.4.18 kernel (plus
> > Trond's seekdir patch, thanks for the help BTW).
> > Ideas anyone ?
> > Thanks in advance,
> Best regards,
> Beowulf mailing list, Beowulf at beowulf.org
> To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
More information about the Beowulf