CfOpenWithOplock error

[kevinchahine]

Expected behaviour

A file on my desktop syncs with the corresponding file on the server.

Actual behaviour

All this is done on the client side.

During sync, owncloud client reports:
CfOpenWithOplock error C:\some\file.~b43 WindowsError: ffffffff80070322: The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken.

And the file is not synced.
When looking at the directory of the locked file, I see hidden files with extensions .~b43 for each locked file.
When manually deleting these files and restarting the sync, the oplock errors usually don’t reoccur.
Other times however, another .~b43 file will be created during the sync process triggering oplock error again.

Steps to reproduce

1. Modify files
2. Save and close files
3. Open ownCloud Client
4. Force a directory to sync
5. oplock error occurs after some time
6. Open directory of problematic files
7. Notice multiple files with extentions .~b43 (one for each locked file)
8. Manually delete these files
9. From owncloud client, force sync again
10. Usually sync works fine. Other times, another .~b43 file is created during sync process triggering an oplock error again.

I think this is a windows problem.

Server configuration

Operating system: Ubuntu 18.04

Web server: Apache/2.4.29 (Ubuntu)

Database: SQL (10.1.47-MariaDB)

PHP version: 7.2.24-0

ownCloud version: 10.7.0 (stable)

Storage backend (external storage): None

Client configuration

Client version: 2.8.2

Operating system: Windows 10 64-bit 2004

OS language: English

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From ownCloud or distro) (Linux only):

Installation path of client:

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

Template for output < 10 lines

1. Client logfile: Output of owncloud --logwindow or owncloud --logfile log.txt
   (On Windows using cmd.exe, you might need to first cd into the ownCloud directory)
   (See also http://doc.owncloud.org/desktop/2.2/troubleshooting.html#client-logfile )

2. Web server error log:

3. Server logfile: ownCloud log (data/owncloud.log):
   CfOpenWithOplock error C:\some\file.~b43 WindowsError: ffffffff80070322: The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken.

• There are multiple of these lines, one for each problematic file.