Re: [PATCH / RFC] nfs-utils: High Availability NFS

[Paul Clements <paul.clements@steeleye.com>]

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