[Samba] incorrect shared access to the file - samba oplock bug?

Jeremy Allison jra at samba.org
Fri Sep 16 04:07:09 GMT 2005

On Thu, Sep 15, 2005 at 03:31:49PM +0400, Jablonovsky Alexander wrote:
> I have tried to read a file from a Windows machine, at time this file 
> being written from a Linux machine with Samba (constantly reading 
> constantly growing file) and got a strange behavior. After reading some 
> number of bytes ReadFile() starts to return 0 bytes read (EOF). Seeking 
> and even closing/reopening the file doesn't help - only the old snapshot 
> of the file can be read. Touching the file from other program like 
> Explorer has effect - Windows refreshes the file to it's current state.

oplocks - either use kernel oplocks or turn off oplock support in Samba.
Also to do this correctly you need byte range lock coordination between
the reading and writing app.


More information about the samba mailing list