[Samba] Re: samba 2.2.3 oplock_break

[Martin Thomas]

There is a problem with overwriting files on Samba 2.2.3
shares which I can reproduce here with servers running Linux.
I've described it in a mail to the list.
(http://lists.samba.org/pipermail/samba/2002-February/065878.html)
Here I do not see oplock failures at debug-level 10 with 
Linux (Kernel 2.4.16). I will try Samba 2.2.3 on an old HP 
workstation running HP-UX 10.20, but this machine needs 
hours to compile...
Checked the WHATSNEW.txt from the tar-file, but
the 3 new smb.conf parameters don't look like they 
'fit' to this issue.

Sorry, I do not have a solutions. But at least I can verify your
findings with very different hardware and OS.

Martin

>  First off thanks for the hard work and great tool.
>  I hope you find this report useful.
>
>   Now, today I installed 2.2.3 on hpux-11 - an attempt to write a file 
>   over a file with same name failed and the file dissapeared totally.
>   There was an error message as well on the pc - running w2k sp2 
>   all MS patches applied.
>
>   The smb log file says:
>
>  [2002/02/03 22:39:06, 0] smbd/oplock.c:(758)
>    oplock_break: receive_smb error (Error 0)
>    oplock_break failed for file Pics/KEEP/mom's cat.jpg (dev = 40030002, inode = 27956, file_id = 1154).
>  [2002/02/03 22:39:06, 0] smbd/oplock.c:(843)
>    oplock_break: client failure in break - shutting down this smbd.
>
>
>   As an aside I had (different) problems with 2.2.2 which I
>   thought had been addressed in this release -  so I was still running
>   2.0.7 which has had no problems at all.
>
>   I compiled with HP's cc compiler - did configure --prefix=/...
>   make ; make install. No other options - perhaps I should have?
>
>   Please let me know if theres anything I can try to avoid this.
>
>   Best regards,
>
>   Gene/


>  Sorry I forgot to mention that I also had the following problem
>  (same system, samba on hpux-11 and pc's runnign w2k-sp2).
>
>  Using file browser I cannot overwrite a file - I get access denied!
>  I can delete the file and write a new one. No errors in the log file
>  for this one.
>
>  This behaviour is definetely new to 2.2.3. Again perhaps this
>  is user error - i copied the config file from the workign 2.0.7.
>  Perhaps I need to set a new option - I could not find anything
>  that seemed directly related tho?
>
>  Regards,
>
>   gene/