You most likely need something like automounter, or maybe amd.
We have seen that with netbsd and carp with nfs, and if you do direct
mounts it tends to make calls on file handles, and directory handles that
the server is not aware of.
Give that FH/DH are session specific.
-Ober
On Wed, 9 Aug 2006, Spruell, Darren-Perot wrote:
Date: Wed, 9 Aug 2006 08:51:59 -0700
From: "Spruell, Darren-Perot" <[EMAIL PROTECTED]>
To: "'misc@openbsd.org'" <misc@openbsd.org>
Subject: NFS high availability
For diskless clients that bootstrap from and mount filesystems from an NFS
server, is it feasible to provide highly-available NFS service using 2
servers in a CARP cluster? A friend reports having tested this out and
having everything work properly on the master, but as soon as CARP failover
occured and I/O requests were sent to the backup node, the client started
throwing "stale nfs file handle" errors. My assumption is that these are the
result of ESTALE being returned by the server and that the system doesn't
understand how to handle this gracefully and reopen the files.
I believe I understand why this occurs, but can't get my head around a good
way to provide fault tolerance in this architecture. How is HA of the NFS
server typically handled, and is CARP an appropriate solution? What other
options are typically used to ensure ongoing client operation if the NFS
server fails?
--
Darren Spruell
Information Security Operations
Catholic Healthcare West IT
(602)307-2217
[EMAIL PROTECTED]
