From: James Pearson <james-p@moving-picture.com>
Subject: Re: Stopping NFS, ip address take over, zero-copy NFS for 2.4.21,
 and misc
Date: Thu, 18 Sep 2003 22:21:37 +0100
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <3F6A21E1.9090404@moving-picture.com>
References: <1063900790.8031.9644.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Cc: nfs@lists.sourceforge.net
To: Chris Worley <cworley@lnxi.com>
Errors-To: nfs-admin@lists.sourceforge.net

Chris Worley 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).
> 
> What am I missing?

I don't know a lot about NFS fail over, but I guess unless the take-over 
server has a copy (or the same copy) of /var/lib/nfs/rmtab, then you 
will get "permission denied" - the server needs an entry for each 
client. I guess it works some of the time as the take-over server has a 
'valid' entry in its rmtab file for that client.

James Pearson


-------------------------------------------------------
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