From: Paul Clements Subject: Re: [PATCH / RFC] nfs-utils: High Availability NFS Date: Fri, 27 Aug 2004 09:13:06 -0400 Sender: nfs-admin@lists.sourceforge.net Message-ID: <412F3362.5040707@steeleye.com> References: <4124DB86.9060505@steeleye.com> <16677.22269.988036.787320@cse.unsw.edu.au> <412E1C10.5020703@steeleye.com> <20040827073049.GA23324@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: Neil Brown , nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1C0gXj-0003rL-Oa for nfs@lists.sourceforge.net; Fri, 27 Aug 2004 06:13:23 -0700 Received: from stat16.steeleye.com ([209.192.50.48] helo=fenric.sc.steeleye.com) by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.34) id 1C0gXj-0005kh-7P for nfs@lists.sourceforge.net; Fri, 27 Aug 2004 06:13:23 -0700 To: Olaf Kirch In-Reply-To: <20040827073049.GA23324@suse.de> Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: Hi, Olaf Kirch wrote: > I'm working on putting statd into the kernel, so I'm necessarily not > too enthusiastic about adding external callouts to statd :) With so many things moving out of the kernel to userland, it's surprising to see statd moving into the kernel. And it certainly does make modifications, such as this, much more difficult. > On Thu, Aug 26, 2004 at 01:21:20PM -0400, Paul Clements wrote: > >>statd events that trigger a callout: >>----------------------------------- >>add client to notify list (SM_MON) - triggers "add-client" callout >> >>delete client from notify list (SM_UNMON and SM_UNMONALL) - triggers >>"del-client" callout > > > I think the same could be achieved by attaching a dnotify handler to > the directory, and it would be compatible with a kernel level statd. But the callout happens before statd replies to the client, so there's no chance that we lose any clients if there's a failure. If we use dnotify then we only find out there's been a change after the change has occurred, which means the client may have already gotten a reply saying he's been added to the notify list. If we get a failure at this point, we've lost a client, and upon failover the client's locks are no longer valid. -- Paul ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs