From: "ian sison (mailing list)" <ian.s@qsr.com.ph>
Subject: An NFS-HA HOWTO anyone? WAS> Re: Stopping NFS, ip address take
 over, zero-copy NFS for 2.4.21, and misc
Date: Sat, 20 Sep 2003 18:22:56 +0800 (PHT)
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <Pine.LNX.4.33L2.0309201819250.29042-100000@jeprox.qsr.com.ph>
References: <291.3f6ac6ae.b6b79@altium.nl>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: <nfs@lists.sourceforge.net>
In-Reply-To: <291.3f6ac6ae.b6b79@altium.nl>
Errors-To: nfs-admin@lists.sourceforge.net


On Fri, 19 Sep 2003 rnews@tasking.nl wrote:

> Chris Worley <cworley@lnxi.com> wrote:
> | 2) IP address takeover between NFS servers.
> |
> | With NFS stateless, and not running lock servers, I thought a simple IP
> | address takeover scheme (when an I/O server goes down, another just adds
> | the failed server's IP address as a virtual interface) would allow
> | clients to immediately renegotiate with the same IP address pointing to
> | another NFS server (serving the same partitions).  The take-over is
> | successful: the clients can communicate with the new I/O server, but I
> | get "permission denied" (as root or otherwise) on the NFS mounted
> | partitions most of the time (sometimes it works).
>
> You need to migrate the entries in /var/lib/nfs/rmtab to the new
> machine. Also, when the device number on the new machine differs
> from the device number on the old machine, you need to use the "fsid"
> option in /etc/exports, to make sure the file handles don't change.

This is important information, and it should go into a howto. NFS-HA is a
very common requirement nowadays, and there's very little information i've
seen on the net except for the Mission Critical Linux site.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs