Good day all...
Quick question - I am using ffs to make 1-click 'backups' of shared folders on a primary tower computer in our house(it mainly functions as a 'file and print server').
The problem is that it is syncing(backing up) a particular share on that computer which I have shared as 'read only', thus reducing the risk of some rogue malware on one of our other pc's could delete the files on that shared folder(it's basically the win10 'Users' folder, so I want it backed up, thus getting everyone's desktop *and* user documents folders. What happens, though, is that every time I run the sync, it returns an error to the effect that it can't create some fffs*.lck file on that share(remember the share is read only) and the status for that sync job always shows as 'failed'(red 'x'), rather than the green checkmark, so I can't see at a glance that it basically happened successfully. Is there like some way to customize where it places that .lck file or some other workaround I can use?
Thanks very much in advance for any tips or suggestions!
-Al
Always an error when syncing...
- Posts: 2
- Joined: 25 Jan 2021
-
- Posts: 2451
- Joined: 22 Aug 2012
Obviously, if there is no write access to a given folder, FFS is not able to write its sync.ffs_lock file(s).
And because of the reason FFS is using sync.ffs_lock files, it is not possible to write those files elsewhere.
Be aware that the notification is a warning, not an error. If you are not running other FFS syncs involving the same folders (or parts thereof), you can safely ignore the warning, and the sync will run normally.
If you are sure there will never be simultaneous FFS syncs that have a full or partial overlap, you can even disable the creation of sync.ffs_lock files.
See LockDirectoriesDuringSync:
And because of the reason FFS is using sync.ffs_lock files, it is not possible to write those files elsewhere.
Be aware that the notification is a warning, not an error. If you are not running other FFS syncs involving the same folders (or parts thereof), you can safely ignore the warning, and the sync will run normally.
If you are sure there will never be simultaneous FFS syncs that have a full or partial overlap, you can even disable the creation of sync.ffs_lock files.
See LockDirectoriesDuringSync:
