samba - Jul 2016 - remove_oplock: failed to lock share entry...

> On Wed, Jun 29, 2016 at 12:11:51PM -0400, Thomas Schulz wrote:
> > 
> > Here is what I could find. The iso file is created on a Solaris system
on
> > a file system that is NFS mounted from our main file server. Then it
is
> > burned to a CD on a Windows 7 PC through a Samba server running on a
> > different Solaris machine (Solaris 10) that is also NFS mounting the
> > file system.
> > 
> > As a test I have tried accessing a newly created iso file created on
the
> > machine that created the subject file and then accessed through the
same
> > Samba server. I can not duplicate the messages. I did not burn the
file
> > to a CD but instad copied it to another location.
> 
> Without a reproducer it's going to be difficult to
> know what the problem is, sorry :-(.
Just got back from vacation....

Under what conditions is an oplock used? I am assuming that it's purpose
is to prevent any changes to a file while the file is in use. Is an oplock
taken whenever a file is opened?

Tom Schulz
Applied Dynamics Intl.
schulz at adi.com

On Thu, Jul 21, 2016 at 10:03:29AM -0400, Thomas Schulz
wrote:
> > On Wed, Jun 29, 2016 at 12:11:51PM -0400, Thomas Schulz wrote:
> > > 
> > > Here is what I could find. The iso file is created on a Solaris
system on
> > > a file system that is NFS mounted from our main file server. Then
it is
> > > burned to a CD on a Windows 7 PC through a Samba server running
on a
> > > different Solaris machine (Solaris 10) that is also NFS mounting
the
> > > file system.
> > > 
> > > As a test I have tried accessing a newly created iso file created
on the
> > > machine that created the subject file and then accessed through
the same
> > > Samba server. I can not duplicate the messages. I did not burn
the file
> > > to a CD but instad copied it to another location.
> > 
> > Without a reproducer it's going to be difficult to
> > know what the problem is, sorry :-(.
> 
> Just got back from vacation....
> 
> Under what conditions is an oplock used? I am assuming that it's
purpose
> is to prevent any changes to a file while the file is in use. Is an oplock
> taken whenever a file is opened?
Yes, most clients do so.