Realtimesync doesn't work with a Network Drive if idle time is above 5

[cogumas]

Hello guys!

I mapped a Drive into windows 10 (shared this folder from a Linux server using SMB) and I mirror this folder into my Google Drive.

Screenshot 2021-12-28 143029.jpg (38.17 KiB) Viewed 973 times

I noticed that RTS just work with my Mapped Drive when I set idle time equal or less then 5. Is this a known behavior?

PS: I created 2 local folders just for test, and RTS works fine set to any idle time.

[xCSxXenon]

I use RTS with an idle time of 60 on a mapped network drive from a Windows host, no issues

[Plerry]

You have RealTimeSync (RTS) monitor the entire Y-drive for changes.
And apparently some program or service makes a change somewhere in your Y-drive every (here) 6 seconds or so. And with your idle-time set to more than 5 seconds, will postpone the execution of your specified sync action by (yet) a further idle-time, during which another change will occur.
It may make sense to divide your RTS monitored folders up in smaller chunks, each monitored by a seperate RTS task and each launching a corresponding FFS sync.

See also viewtopic.php?t=8983&p=32307#p32307 and viewtopic.php?t=7106&p=23669#p23669

[laritibouilla]

Hi
Y also notice the same kind of behaviour
I get it after switching my share Drive from SMB1 (SMB V1) to SMB2 (SMB V2/V3) protocol.
SMB1: everything is working fine
SMB2: Error message: ERROR_INVALID_FUNCTION: Fonction incorrecte. [GetOverlappedResult]).
When switching back to SMB1 everything is working.
Now the Protocol is SMB2 (SMB V2/V3) and I reduce the idle to “0”. Outcome: time to time the Sync is working then crashing, then wokring... Weird, but at least I have a workhour