Good old file locking

[Steve Gray]

I am noticing a problem with Samba not dropping/removing file locks. Here's what 
I've got:

Samba 2.0.6 on a Sun E450 running Solaris 2.6
PC running Win95 and WordPerfect 8

smb.conf is pretty much standard, with oplocks enabled.

Here's what happens:

A user will open a file, the lock will be set, and even when the file is closed, 
the lock remains (as confirmed by smbstatus). The next time the user goes to 
open the file, it's locked.

I perused the client's smb log, and is show this, which might be helpful:

-----------
[2000/07/17 14:12:41, 0] smbd/oplock.c:(974)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file files/118/2128000.wp8 (dev = 1540014, inode = 
310240).
[2000/07/17 14:12:41, 0] smbd/oplock.c:(1048)
  oplock_break: client failure in oplock break in file files/118/2128000.wp8
-----------  

I'm unsure if this happens while the file is open, or when the second attempt is 
made to open (thus encountering the lock). Actually, since I'm seeing 2 PIDs, 
I'm suspecting that this is one of each, right at the point of failure.

Any ideas on what to do? I tried to search the archives, but it looks like 
they're hosed up. I really don't want to turn oplocks off, but I will if I have 
to.

Thanks,

Steve Gray
sagray at tycoelectronics.com