From: "Ragnar Kjørstad" <nfs@ragnark.vestdata.no>
To: Bruce Allan <bruce.allan@us.ibm.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs-utils patch to statd for multi-homed hosts
Date: Sat, 1 Jun 2002 12:27:23 +0200 [thread overview]
Message-ID: <20020601122723.F3799@vestdata.no> (raw)
In-Reply-To: <OFE81A6846.D2A070A1-ON88256BCA.006D5F8B@boulder.ibm.com>; from bruce.allan@us.ibm.com on Fri, May 31, 2002 at 01:18:27PM -0700
On Fri, May 31, 2002 at 01:18:27PM -0700, Bruce Allan wrote:
> The attached patch provides the capability for statd to work with
> multi-homed hosts (i.e. NFS servers and clients with more than one IP
> interface each) as until now listed as a "FIXME" comment in
> utils/statd/rmtcall.c
Great! :-)
> The theory is when a server or client crashes, reboots, and attempts to
> notify the other of it's status change, if either host's interface on w=
hich
> the connection was originally made is no longer functional, statd will
> attempt to use alternate interfaces if they exist. This is made possib=
le
> by changing the addr member of the notify_list structure to a list of
> addresses equivalent to that returned by a gethostbyname() call. Faile=
d
> attempts at notifying an address removes that address from the list.
Are you saying notifications used to be sent out on the interface where
the connection happened? I thought it only happened on the primary
interface....
Does the new code work with aliases as well as physical interfaces?
How does this interact with the "--name" switch?
I believe --name originally replaced the gethostbyname() name with the
user-supplied one. Now that there are multiple interfaces to worry about
the old approach no longer works well.
I see a few different alternatives of fixing that:
1. Remove "--name". It was mostly written to fix the exact same problem
that your patch fixes in a bettery way. Unfortenately this will not
solve the problem with multiple names mapping to the same ip.
2. Change "--name" so that it _adds_ the hostname to the list of
names to use in the notification-message, rather than replacing
the existing one(s). I suppose it should also be changed to accept
mulitple hostnames.
3. Could we possible send the IP to the clients rather than the
hostnames? That would eliminate the problem of mulitple names
matching the same hostname.
I suppose I should go read the spec and find out how this really work
before making comments, but I don't have the time just now, so take the
comments with a grain of salt..
--=20
Ragnar Kj=F8rstad
Big Storage
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-06-01 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 20:18 nfs-utils patch to statd for multi-homed hosts Bruce Allan
2002-06-01 10:27 ` Ragnar Kjørstad [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 22:13 Bruce Allan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020601122723.F3799@vestdata.no \
--to=nfs@ragnark.vestdata.no \
--cc=bruce.allan@us.ibm.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox