Janne Karhunen wrote:
On Fri, May 2, 2008 at 11:21 AM, Wendy Cheng <s.wendy.cheng@xxxxxxxxx> wrote:
After browsing thru "statd -n" flow, it is still not clear what will happen
if there are more than 2 interfaces used to export NFS shares ?
How come? It will use the interface specified with -n.
ok, just read your follow-on email .. so we can cross out this one.
Using "statd -H", together with patches described in:
https://www.redhat.com/archives/cluster-devel/2007-April/msg00028.html ,
So this basically makes it a users problem, I don't
like it. Statd's standard notifications are just fine and
I don't want to have anything to do with the process.
It should work as is, out of the box, without writing
separate programs to handle stuff that statd doesn't
do.
I think you mis-understand our approach. With our patch, you do *not*
need to do anything if you have only one single (floating) interface to
do nfs export (and you can have the machine configured to use other
hostname). The statd's "my_name" is correctly filled (from kernel by our
patch) - it is no longer bound to 127.0.0.1.
Maybe I mislead you in previous post. The "-H" is only an "example" - to
show people how to selectively move an ip address around without
affecting other co-existing nfs ip interface on the same server. I did
plan to submit a complete user mode patch so the program after "-H" will
have a default executable (but user still can use their own if they
don't like our nlm directory structure).
our cluster failover (with 4 IP interfaces per server) seemed to run well
without troubles.
Your idea was to serve traffic via all of these interfaces?
yes ...
One specific segment is just enough for us.
I know .. but there *are* users and live systems *today* that have
multiple nfs interfaces. For big-fat server, I normally saw 4.
Our servers
can have anything from 5 - 100 floating addresses and
it would be just great if we could keep each service
bound in it's own address. It's just better that way.
To me these use cases are clearly different. You're
trying to serve traffic to multiple segments and need
stuff that 'user have to worry about' to accomplish
this. -n works as is for just one segment. And how
many users really need interface specific selective
grace anyway?
I hope above clears the confusion ? Again, admin(s) do *not* need to do
anything if there is only one single (floating) nfs export IP address.
On the other hand, we did see systems had many nfs interfaces (I was
surprised too). And that was exactly the rationale to kick off this work
three years ago .
-- Wendy
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
