Oplock file corruption problem

[Joel Hammer]

Oplocks allows local caching of the file being used on the windows client. 
We are seeing a lot of file corruption reported on this mailing list.
Oplocks, which makes samba more efficient, seem to be often involved.
I would turn oplocks off. They are on by default. You can also veto oplocks
for certain file types.
Joel
On Wed, Dec 05, 2001 at 12:01:18PM -0500, Kevin wrote:
> This morning one of my users complained that an *.xls
> file she was working on yesterday was now corrupt.  I
> checked the samba logs and found this in the log for
> her machine.  The file referenced here is the file that
> is now corrupt.
> 
> 
> [2001/12/04 19:47:22, 0]
> smbd/oplock.c:oplock_break(786)
>   oplock_break: receive_smb timed out after 30 seconds.
>   oplock_break failed for file Forms/Net Worth and
> assoc forms.xls (dev = 804, inode = 71466586).
> [2001/12/04 19:47:22, 0]
> smbd/oplock.c:oplock_break(859)
>   oplock_break: client failure in oplock break in file
> Forms/Net Worth and assoc forms.xls
> [2001/12/04 19:47:22, 0]
> smbd/reply.c:reply_lockingX(4413)
>   reply_lockingX: Error : oplock break from client for
> fnum = 13241 and no oplock granted on this file
> (Forms/Net Worth and assoc forms.xls).
> 
> 
> Unfortunately, i know nothing about oplocks and
> consequently do not know how to interpret the info in
> the log.  Can anyone tell what happened from the log
> entry, and more importantly, what i should do to ensure
> that it does not happen again?
> 
> The server is TurboLinux 6.5 and Samba 2.2.2 running on
> an XFS 1.0.1 file system.  The client is a Win2K box on
> an NT domain.
> 
> 
> Thanks a million.
> 
> VeKTeReX
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba