[Samba] File locking problem involving Samba, Clearcase, and Cygwin

Kathy banshee135 at gmail.com
Tue Apr 21 22:36:39 GMT 2009

I wanted to send a final post about this issue.  I apologise for not
responding until 2 months later.  For those interested, we ended up
just writing our logs to a Samba share that was outside of a Clearcase
share and we had no further issues with files being locked.  So....
that says that Clearcase did indeed have something to do with the
issue in how it was playing with Samba, but having them write logs to
another location was a lot easier solution than trying to debug it
further.  Our engineering department has tight schedules, so we went
with the easy fix.  I am still using the version of Samba that Jeremy
suggested (3.2.8) but I suspect that it would have worked okay with
the original 3.0.28 if we were writing elsewhere than the Clearcase

Thanks for all the help you gave me back in February about this
problem.  I do appreciate it.


On Tue, Feb 10, 2009 at 7:56 PM, Jeremy Allison <jra at samba.org> wrote:
> On Tue, Feb 10, 2009 at 02:24:10PM -0800, Kathy wrote:
>> I wanted to post again with the results of using Samba 3.2.8.  Looks
>> like this did not solve our "locking" problem.  We are still getting
>> permission denied errors when we try to do a "mv" of a log file inside
>> a Clearcase view via a Samba share to a different location.  Again,
>> this is inside a Cygwin window on a WindowsXP virtual machine.  It is
>> referencing a Clearcase dynamic view via Samba on
>> //server/<view_name>.   It does not matter if you try to move it to
>> another Clearcase view (i.e. //server/views/<ccase_view_name/<dir>) or
>> if you try to move it to a Windows share or even to the local drive.
>> Below is a snippet of what the Samba log shows when these two files
>> can't be moved.  ProcessExplorer program on the Windows XP machine did
>> not show file handle holding on to either of these files.  Smbstatus
>> on the RHEL 5.2 Clearcase/Samba server reported NONE for oplocks,
>> WRONLY for R/W, and DENY_NONE on DenyMode.
>> We are now running new tests where the scripts are writing the logs to
>> a Samba share, but not to a share that is also a Clearcase view.  And
>> if we still have issues we are going to then have the logs write to a
>> local drive, leaving Samba completely out of it for the part of
>> writing logs.  (They will still be inside the CC view via Samba when
>> firing off their scripts.)
> Ok, thanks for testing with the latest code. As Volker
> mentioned, what we need now if for you to test this
> against a Windows 2003 or 2008 server and see if this
> reproduces the problem. If not, a wireshark network
> trace of it working correctly against Windows 200[3|8]
> and it not working correctly against Samba 3.2.8 is
> needed.
> Thanks a lot,
> Jeremy.

More information about the samba mailing list