Cannot write file "C:\sync.ffs_lock"

[Alerio]

hello, i got this warning

Errors and warnings:
________________________________________
[1:01:01 AM] Warning: Cannot set directory locks for the following folders:
Cannot write file "C:\sync.ffs_lock".
ERROR_ACCESS_DENIED: Access is denied. [CreateFile]
________________________________________

i assume because it is the windows c: drive

however, in my sync task i do not actually sync anything in the root c folder.

The sync task is configured like this:

Source folder: C:\
destination folder: Z:\
include:
\some\folder
\some\other\folder
exclude: none

note that

*

is not included. all the folders that are included sync fine and do not generate a warning


my question is why is ffs trying to write a lock file in the root folder even though nothing in the root folder is being synced?

and suggestion it should only write to locations that are actually being synced

thanks!

[Plerry]

Instead of using a single left-right base-folder pair, C:\ <=> Z:\ you could use:

Assuming \some1 and \some2 are different:
use two folder pairs
1) C:\some1\folder <=> Z:\some1\folder
2) C:\some2\other\folder <=> Z:\some2\other\folder
and a simple Include Filter *.
In order to prevent the sync.ffs_lock fil warning, you obviously then need to have write access to C:\some1\folder and C:\some2\other\folder (and its Z-drive counterparts), but no longer to the root of C:\

Assuming \some1 = \some2 = \some
use a single left-right base folder pair
C:\some <=> Z:\some
and an Include Filter
\folder
\other\folder
In order to prevent the sync.ffs_lock fil warning, you obviously then need to have write access to C:\some (and its Z-drive counterpart), but no longer to the root of C:\

[xCSxXenon]

Along with Plerry's correct suggestion, I'll add that the root "issue" is that the lock file is placed in the root of the locations, regardless of filters/settings

[Alerio]

Along with Plerry's correct suggestion, I'll add that the root "issue" is that the lock file is placed in the root of the locations, regardless of filters/settings

thanks for confirming this is the behaviour. i guessed but wasn't sure.

so currently if i want to have the base folder just be the root of the drives and customize with the include/exclude filters it'll always put the lock file in the base folder

i guess i have 2 questions then:

1. i must assume this behaviour was chosen because of some desirable characteristic, instead of putting the Lock file in the folder that is actually currently being worked on. in other words, there's no chance of this behaviour changing any time soon right?

2. another workaround is to disable placing the lock file. I've reviewed the help file section on this which notes that the purpose is to prevent concurrent sync jobs, mainly intended for network shares. i am doing this on a local machine to a usb hdd. is there anything else i should beware about or other issues with disabling the lock file?


thanks for your help!

[Plerry]

1) Correct. As discussed multiple times in this forum.

2) If there will never be any other, concurrent FFS syncs involving C:\ (and/or Z:\) you should be safe to not use the lock files.