Am doing large sync job with 9 local source directories and remotes via SFTP to NAS drive; 450+ total GB; all are Mirror-to-right; included are Dropbox and Google Drive directories. Throughout the sync, sync.ffs_lock keeps being updated in Dropbox and Google Drive, even with sync paused. Is this normal?
I also found this which may be a viable solution but wanted to see if pausing should also pause modification of sync.ffs_lock
sync.ffs_lock continually updated even when sync paused
- Posts: 1
- Joined: 12 Apr 2010
-
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
Yes this is normal. Were they not updated, a second FFS instance could decide these lock files are abandoned and incorrectly take ownership of the lock.
In general if you don't need the folder lock, you can always disable it, but in more complex scenarios it is easy to miss sync dependencies that the locking would serialize. So as long as there is no significant drawback due to the lock files, I'd suggest to keep them active.
In general if you don't need the folder lock, you can always disable it, but in more complex scenarios it is easy to miss sync dependencies that the locking would serialize. So as long as there is no significant drawback due to the lock files, I'd suggest to keep them active.
