On Mon, Nov 18, 2002 at 04:41:37PM -0600, Jesse Pollard wrote:
> Actually, I was thinking that each server served a different mountpoint
> instead of both providing the same one.
I know.
> I'm not sure how the locks currently would be provided unless the
> distributed lock from the shared storage interacts with each servers statd
> properly. Otherwise you will already have problems.
"The distributed lock"? Are you talking about scsi-level locks?
No, there is no link between the locks on the lower levels and NFS.
> Second, I thought that statd didn't care about the lock requests coming
> from two IP numbers. This should be no different than having two network
> interfaces attached to one server (and that works under Solaris). The
> client should be using the name from the IP number, not the router used
> between the client and server. I view the floating IP as existing behind
> a router using the real IP. Since none of the clients are using the real
> IP, the naming should remain consistant (I think).
Yes, it's simular to having two network interfaces on one server. If it
works on solaris then clearly it can be make to work on linux as well.
Older versions of nfs-utils used only the IP from
gethostbyname(gethostname); Clearly that didn't work for setups like
this.
I wrote a patch that made it possible to change the IP-address to a
"service-IP". That allowed us to do failover like described in an
earlier mail.
Later that feature has been extended and modified by others. It is
possible that it now allows multiple IP-addresses. If that's the case,
then half the problem is solved.
The other half remains though.
-- Ragnar Kjørstad Big Storage - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:25 EST