From owner-freebsd-cluster Tue Apr 30 7:43:44 2002 Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.21]) by hub.freebsd.org (Postfix) with SMTP id 20B4A37B420 for ; Tue, 30 Apr 2002 07:43:42 -0700 (PDT) Received: (qmail 56491 invoked from network); 30 Apr 2002 10:43:41 -0400 Received: from unknown (172.16.0.181) by mx1.backend.thebiz.net with QMQP; 30 Apr 2002 10:43:41 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Apr 2002 14:43:41 -0000 Date: Tue, 30 Apr 2002 10:43:41 -0400 (EDT) From: Brandon Poyner X-X-Sender: bpoyner@staff.noc.thebiz.net To: freebsd-cluster@freebsd.org Subject: NFS failover Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-cluster@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to design a diskless cluster of clients that boot off 2 "master" servers. I want one master server to take over all NFS responsibilities when the other master server is down. The real problem is that the root NFS mount points on the clients do not fail over gracefully. They still have the old filehandle from the master server that is down and are stubborn to let it go and try contacting portmap again. Is there something simple I'm missing, like a timeout option? -- Brandon Poyner, Unix Systems Engineer brandon@veranet.net VeraNet Solutions, a BiznessOnline.com Company http://www.veranet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message