From: Jeff Layton <jtlayton@poochiereds.net>
Subject: Re: Q: NFS server cluster
Date: Sat, 01 Apr 2006 07:16:06 -0500
Message-ID: <1143893766.13560.9.camel@localhost.localdomain>
References: <20060331160217.1734f710@mwdsp001.swissptt.ch>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: Chris Osicki <osk@admin.swisscom-mobile.ch>
In-Reply-To: <20060331160217.1734f710@mwdsp001.swissptt.ch>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

On Fri, 2006-03-31 at 16:02 +0200, Chris Osicki wrote:
> Is there anything I can do to eliminate this behaviour?
> If I understand correctly the problem is on the server side for the
> client nothing changes, the same IP-address to talk to, the same
> filesystem/filehandle. Or am I missing something.
> 

Be sure the blockdev has the same device major/minor number on both
hosts, though it sounds like you may already have checked that.

Otherwise, this sounds a lot like an issue with ARP. When you float IP
addresses you need to have the new address owner send gratuitous ARPs so
that its neighbors update their caches. Make sure your failover software
is doing this, and that the client and/or router isn't ignoring them.

-- Jeff


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs