From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wendy Cheng Date: Tue, 10 Apr 2007 14:16:59 -0400 Subject: [Cluster-devel] Re: [NFS] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes In-Reply-To: <200704101109.44333.okir@lst.de> References: <46156FA0.4030506@redhat.com> <200704101109.44333.okir@lst.de> Message-ID: <461BD49B.7090503@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Olaf Kirch wrote: > But - why do you need to record the address on which the request was > received. at all? Don't you know beforehand on which IP addresses you > will be servicing NFS requests, and which will need to be migrated? > > Sorry, somehow I missed this question ... The intent is to avoid sending notifications to *all* clients. The cluster user mode scripts will have to associate the floating IP(s) with fsid(s) and relies heavily on the information passed by rpc.statd's ha-callout program. My test ha-callout user mode program shows the following: /mnt/lockd/ha-pg/hatest is invoked with 3 arguments. add-client 192.168.24.146 192.168.24.149 /mnt/lockd/ha-pg/hatest is invoked with 3 arguments. del-client 192.168.24.145 192.168.24.149 These info(s) will be used to construct the notification list when notification actually take places. -- Wendy