Re: file leases

["William A.(Andy) Adamson" <andros@citi.umich.edu>]

> Stephen Rothwell wrote:
> > > > When I share a directory using Samba 3.0.6, sometimes local access to
> > > > a file stalls for a while - on the order of 10 seconds to open a file.
> > > 
> > > if your open() is blocking (did not specify O_NONBLOCK) then
> > > break_lease will contact all other processes (samba clients) one
> > > at a time, and will not return until all have been contacted. this
> > > could take a while.
> > 
> > And, of course, the samba servers may have to contact their clients and
> > get them to release their oplocks ...
> 
> Quite, but the client is a Windows 2000 box completely idle with
> nothing holding the file open, and a good LAN connection.
> 
> If an idle client won't release oplocks quickly on request, then
> there's a problem.  

it's not a bug, it's a feature! the open from the idle windows box is stalled 
at the server while the server sends break_lease messages to all the other 
clients with op locks on the file. that is the promise of op locks.

> Surely people using lots of Windows clients don't
> have to wait 10 seconds or more to open a file which somebody else had
> open recently on a different box?  I suspect a Samba problem but
> anyways the answer is to disable oplocks.  It _could_ be a fault in
> leases, which is why I asked if they're known to be working.
> 
> -- Jamie
>