sync.ffs_lock ERROR_SHARING_VIOLATION

[axel72]

Hi all,

I am running a one-way-sync (batched) every 15 minutes on folders with minor changes. Most of the time, this runs well without issues. From time to time, I receive repeatedly errors like those:

<snipp>
Die Datei "x:\folder\sync.ffs_lock" kann nicht geschrieben werden.
ERROR_SHARING_VIOLATION: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird. [CreateFile]
</snipp>

I tried to exclude it, but no luck, whatever I try.
If ran manually, the error does not occur.

Of course I searched the forum, but could not find any hints.

Any ideas?
Should I translate above's German error message?

As this is a quick run normally (17s), I do not think it is overlapping.
64.408 Elemente gefunden | Vergangene Zeit: 00:00:17

Thanks for all help you can send.

BR
Axel

[xCSxXenon]

Since it shows an 'X' drive, I am assuming this is network storage of some kind. I'm guessing something is running on your system or that system that is holding the lock file for further processing. virus scanning, versioning, hashing, it could literally be anything, it's not mine to say lol
The lock file is something FFS uses to prevent multiple sessions from running on the same location at the same time. They can be disabled, but they cannot be excluded via filters.

[axel72]

Understood, thanks a lot. As an information for others, actually 'x' is a drive connected to a cloud sync, and your information transferred to this obviously means some _contineous_ file access is happening, which -- even if surprising -- this does not happen often in my case.

I was wondering because if at all, this happens (1) for hours and (2) when no backup etc. is running. Following your hints, this could be anything. I will observe this, even if I am not sure I will really find the cause. But if yes, I want to to share this here. Looks like Windows sysinternals / "handle.exe" could help, following some AI help.

BR
Axel