From owner-freebsd-questions@FreeBSD.ORG Mon May 31 10:35:46 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9851316A4CE for ; Mon, 31 May 2004 10:35:46 -0700 (PDT) Received: from watcher.puryear-it.com (ip-66-186-248-99.static.eatel.net [66.186.248.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7328143D2D for ; Mon, 31 May 2004 10:35:46 -0700 (PDT) (envelope-from dap99@i-55.com) Received: from localhost (unknown [127.0.0.1]) by watcher.puryear-it.com (Postfix) with ESMTP id 6451934D6D; Mon, 31 May 2004 12:30:35 -0500 (CDT) Received: from watcher.puryear-it.com ([127.0.0.1]) by localhost (watcher.puryear-it.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65125-08; Mon, 31 May 2004 12:30:33 -0500 (CDT) Received: from yourqqh4336axf (localhost [127.0.0.1]) by watcher.puryear-it.com (Postfix) with SMTP id 5C75E34D1E; Mon, 31 May 2004 12:30:33 -0500 (CDT) Message-ID: <01a901c44735$9c563270$6501a8c0@yourqqh4336axf> From: "adp" To: "Chuck Swiger" References: <011401c446ae$3aa4cff0$6501a8c0@yourqqh4336axf> <40BB6376.8030704@mac.com> Date: Mon, 31 May 2004 12:33:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300 X-Virus-Scanned: by amavisd-new cc: questions@freebsd.org Subject: Re: NFS server fail-over - how do you do it? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2004 17:35:46 -0000 Very useful information, thanks. We have a very stable NFS server, but I am still working hard to put some redundancy into place. I was thinking that since NFS is udp-based, that if the primary NFS server failed, and the secondary assumed the primary NFS server's IP address, that things would at least return to normal (of course, any writes that had been in progress would fail horribly). That doesn't seem to be the case. During a test we killed the main NFS server and brought up the NFS IP as an alias on the backup. Didn't work. Has anyone tried anything like this? ----- Original Message ----- From: "Chuck Swiger" To: "adp" Cc: Sent: Monday, May 31, 2004 11:55 AM Subject: Re: NFS server fail-over - how do you do it? > adp wrote: > > One of my big problems right now is that if our primary NFS server goes down > > then everything using that NFS mount locks up. If I change to the mounted > > filesystem on the client then it stalls: > > > > # pwd > > /root > > # cd /nfs-mount-dir > > [locks] > > > > If I try to reboot the reboot fails as well since FreeBSD can't unmount the > > filesystem!? > > Solaris provides mechanisms for NFS-failover for read-only NFS shares, but > FreeBSD doesn't seem to support that. Besides, most people seem to want to > use read/write filesystems, which makes the former solution not very useful to > most people's requirements. > > The solution to the problem is to make very certain that your primary NFS > server does not go down, ever, period. Reasonable people who identify a > mission-critical system such as a primary NFS server ought to be willing to > spend money to get really good hardware, have a UPS, and so forth to facility > the goal of 100% uptime. A Sun E450 still makes a nice primary fileserver, > although NAS solutions like a NetApp or an Auspex (not cheap!) should also be > considered. > > The other choice would be to switch from using NFS to using a distributed > filesystem which implements fileserver redundancy, such as AFS and it's > successor, DFS. > > -- > -Chuck > >