From owner-freebsd-isp Sat Apr 28 9:55:18 2001 Delivered-To: freebsd-isp@freebsd.org Received: from velvet.sensation.net.au (serial1-2-velvet-brunswick.sensation.net.au [203.20.114.195]) by hub.freebsd.org (Postfix) with ESMTP id 16A9637B422 for ; Sat, 28 Apr 2001 09:55:02 -0700 (PDT) (envelope-from rowan@sensation.net.au) Received: from localhost (rowan@localhost) by velvet.sensation.net.au (8.9.3/8.9.3) with ESMTP id CAA22938 for ; Sun, 29 Apr 2001 02:54:26 +1000 (EST) (envelope-from rowan@sensation.net.au) X-Authentication-Warning: velvet.sensation.net.au: rowan owned process doing -bs Date: Sun, 29 Apr 2001 02:54:24 +1000 (EST) From: Rowan Crowe To: freebsd-isp@freebsd.org Subject: "failsafe" NFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I've just started reading up on, and playing with NFS. Is it possible to use multiple servers, like HD mirroring? For example a passive second server quietly writes all changes to its local HD, but ignores read requests - unless the first server is unresponsive. I don't know if this could be kludged together easily with front end packet redirection and some hacks to the server code, or whether the NFS protocol itself maintains state information between the client and server that will be broken if another server is seamlessly switched in... Thoughts? BTW, I've found NFS works surprisingly well over a 512:2048kbit DSL link (server and client on the LAN at each end of that link), through no less than *two* IPIP/NOS tunnels (fragmented fragments!) BTW2, I know NFS is primarily for fast LANs, but does it use any data caching to minimise repetitive network activity for commonly loaded data? FreeBSD at both ends in this case. Cheers. -- Rowan Crowe http://www.rowan.sensation.net.au/ Sensation Internet Services http://info.sensation.net.au/ Melbourne, Australia Phone: +61-3-9388-9260 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message