cifs: file locking problem

[spotlight2001]

The problem can be described as follow:

1) mount cifs drive, alfresco 2.9c
OR alfresco 2.9B
(2.9c has the refactored jlan code)

2) copy a text file named a.txt to cifs
3) edit the textfile with UltraEdit (this is important, because UE creates a BAK file on save; other programs might produce the same effect) and SAVE
4) there is an a.txt and an a.txt.bak file
5) now the PROBLEM: you can read and edit a.txt.bak but NOT a.txt itself !
6) after 60 seconds a.txt is readable , before it is not even readable

Is this a configuration problem or a problem with the CIFS code ?
Is there a solution for this problem ?

This does e.g. not occur with NOTEPAD as that program does not create a BAK file.

My suspicion is: the original a.txt is moved to a.txt.bak and somehoow the new a.txt iis affected by the described problem.

This does not occur on your local hard drive and not on usual network shares!

[spotlight2001]

thanks for the answer.

There is no hint in the logs, which would shed light on what might cause this.
Basically it boils down to the following "feature": you can only save once per minute on CIFS (within certain applications).

kind regards

[spotlight2001]

the same problem seems to be described also in post http://forums.alfresco.com/en/viewtopic.php?f=4&t=13634&start=0&st=0&sk=t&sd=a&hilit=cifs+lock#p4481...

[spotlight2001]

some more interesting(?) details:
* if I rename the parent directory of the locked (i.e. UNREADABLE) file, the locked file can be read.
* if the directory is renamed back to the name it had before, the file is locked again.

I am not sure, but somehow things seem to point to the org.alfresco.jlan.server.filesys.cache package.

This "functionality" severely inhibits productive working with Alfresco CIFS.

[spotlight2001]

I noticed, that a "lock manager" (not sure how it is really called) was introduced in spring 2007 in order to prevent concurrent editing of Word-Dokuments.

I can rather accept concurrent editing (use check-out!) than users not being able editing their own files.

Would it be a correct way to circumvent this problem by commenting out the "lock manager" introduced in 2007 ?

[spotlight2001]

* problem solved by backport of LATEST alfresco 3.0 beta 2 code to 2.9C dev (db schema 118).
* alfresco 3.0 beta 2 was not usable bec. it does NOT run in JBoss (yet)

Alfresco team apparently solved the problems during July acc. to SVN.

A hint like : "we have solved that finally in 3.0 Beta" or similar would have been helpful.

hard work, but definitely the advantages of open source!