I run Syncthing bethween Windows 10 and Openmediavault, on all the folders I checked “Watch for Changes” but them never sync automatically, I have to go on Synctrayzor and click rescan all directories.
Anybody have the same problem?
Usually a problem because the data lives on a filesystem that does not support watches for changes.
On Win10 obviously ntfs and on Debian ext4. There is something that could I do?
Is the data actually in ntfs? Or is something that is mounted?
Suggest you check the logs.
Sorry but I’m not sure to understand what do you mean.
When I copy a new file I see the Synctrayzor icon turn after some seconds but on the nas the file never appear. So I have to click “rescan all directories” and I see immediatly the file in the nas. When I do this I have this log on Synctrayzor:
SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
Yeah, thats synctrayzor log, I think you should check syncthing log.
This is Syncthing (nas) log:
[GNCGI] 08:44:12 INFO: Paused state detected, possibly woke up from standby. Restarting in 1m0s.
[GNCGI] 08:44:12 INFO: Connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: read timeout
[GNCGI] 08:44:12 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[GNCGI] 08:44:12 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[GNCGI] 08:44:12 INFO: listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: could not find a connectable relay
[GNCGI] 08:44:12 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[GNCGI] 08:44:12 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[GNCGI] 08:44:12 INFO: listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp: lookup relays.syncthing.net: no such host
[GNCGI] 08:44:12 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[GNCGI] 08:44:12 INFO: listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get "https://relays.syncthing.net/endpoint": dial tcp: lookup relays.syncthing.net: no such host
[GNCGI] 08:45:12 INFO: QUIC listener ([::]:22000) shutting down
[GNCGI] 08:45:12 INFO: TCP listener ([::]:22000) shutting down
[GNCGI] 08:45:12 INFO: Exiting
[monitor] 08:45:14 INFO: Log output saved to file "C:\Users\Workstation\AppData\Local\Syncthing\syncthing.log"
[start] 08:45:14 INFO: syncthing v1.18.3 "Fermium Flea" (go1.17.1 windows-amd64) teamcity@build.syncthing.net 2021-09-28 06:05:18 UTC
[start] 08:45:14 INFO: Using large-database tuning
[GNCGI] 08:45:14 INFO: My ID: GNCGIAW
[GNCGI] 08:45:15 INFO: Single thread SHA256 performance is 1814 MB/s using minio/sha256-simd (490 MB/s using crypto/sha256).
[GNCGI] 08:45:16 INFO: Hashing performance is 1173.33 MB/s
[GNCGI] 08:45:16 INFO: Overall send rate is unlimited, receive rate is unlimited
[GNCGI] 08:45:16 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[GNCGI] 08:45:16 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX
[GNCGI] 08:45:16 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX
[GNCGI] 08:45:16 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX
[GNCGI] 08:45:16 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[GNCGI] 08:45:16 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[GNCGI] 08:45:16 INFO: QUIC listener ([::]:22000) starting
[GNCGI] 08:45:16 INFO: TCP listener ([::]:22000) starting
[GNCGI] 08:45:16 INFO: Ready to synchronize "Archivio personale" (kfpbb-gurkw) (sendreceive)
[GNCGI] 08:45:16 INFO: Ready to synchronize "Archivio studio" (pzsud-nnkxr) (sendreceive)
[GNCGI] 08:45:16 INFO: GUI and API listening on 127.0.0.1:8384
[GNCGI] 08:45:16 INFO: Access the GUI via the following URL: http://localhost:8384/
[GNCGI] 08:45:16 INFO: My name is "Workstation 1"
[GNCGI] 08:45:16 INFO: Device LBZU575 is "Nas" at [dynamic]
[GNCGI] 08:45:17 INFO: Established secure connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 08:45:17 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 08:45:19 INFO: Completed initial scan of sendreceive folder "Archivio personale" (kfpbb-gurkw)
[GNCGI] 08:45:19 INFO: Completed initial scan of sendreceive folder "Archivio studio" (pzsud-nnkxr)
[GNCGI] 08:45:26 INFO: Detected 0 NAT services
[GNCGI] 08:45:26 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[GNCGI] 08:46:04 INFO: Joined relay relay://192.33.91.248:22067
[GNCGI] 09:40:05 INFO: Joined relay relay://130.61.99.81:22067
[GNCGI] 15:41:48 INFO: Paused state detected, possibly woke up from standby. Restarting in 1m0s.
[GNCGI] 15:41:49 INFO: Connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: read timeout
[GNCGI] 15:41:50 INFO: Pausing LBZU575
[GNCGI] 15:41:51 INFO: Resuming LBZU575
[GNCGI] 15:41:51 INFO: Joined relay relay://212.101.20.53:80
[GNCGI] 15:42:08 INFO: Established secure connection to LBZU575 at 192.168.1.129:49351-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:08 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:49351-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:11 INFO: Established secure connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:11 INFO: Replacing old connection 192.168.1.129:49351-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 with 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 for LBZU575
[GNCGI] 15:42:11 INFO: Connection to LBZU575 at 192.168.1.129:49351-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: replacing connection
[GNCGI] 15:42:11 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:48 INFO: QUIC listener ([::]:22000) shutting down
[GNCGI] 15:42:48 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[GNCGI] 15:42:48 INFO: Connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: Syncthing is being stopped
[GNCGI] 15:42:49 INFO: TCP listener ([::]:22000) shutting down
[GNCGI] 15:42:49 INFO: Exiting
[monitor] 15:42:49 INFO: Log output saved to file "C:\Users\Workstation\AppData\Local\Syncthing\syncthing.log"
[start] 15:42:49 INFO: syncthing v1.18.3 "Fermium Flea" (go1.17.1 windows-amd64) teamcity@build.syncthing.net 2021-09-28 06:05:18 UTC
[GNCGI] 15:42:50 INFO: My ID: GNCGIAW
[GNCGI] 15:42:51 INFO: Single thread SHA256 performance is 1831 MB/s using minio/sha256-simd (493 MB/s using crypto/sha256).
[GNCGI] 15:42:51 INFO: Hashing performance is 1173.29 MB/s
[GNCGI] 15:42:51 INFO: Overall send rate is unlimited, receive rate is unlimited
[GNCGI] 15:42:51 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[GNCGI] 15:42:51 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX
[GNCGI] 15:42:51 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX
[GNCGI] 15:42:51 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX
[GNCGI] 15:42:51 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[GNCGI] 15:42:51 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[GNCGI] 15:42:51 INFO: Ready to synchronize "Archivio personale" (kfpbb-gurkw) (sendreceive)
[GNCGI] 15:42:51 INFO: Ready to synchronize "Archivio studio" (pzsud-nnkxr) (sendreceive)
[GNCGI] 15:42:51 INFO: TCP listener ([::]:22000) starting
[GNCGI] 15:42:51 INFO: QUIC listener ([::]:22000) starting
[GNCGI] 15:42:51 INFO: GUI and API listening on 127.0.0.1:8384
[GNCGI] 15:42:51 INFO: Access the GUI via the following URL: http://localhost:8384/
[GNCGI] 15:42:51 INFO: My name is "Workstation 1"
[GNCGI] 15:42:51 INFO: Device LBZU575 is "Nas" at [dynamic]
[GNCGI] 15:42:53 INFO: Established secure connection to LBZU575 at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:53 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:42:54 INFO: Completed initial scan of sendreceive folder "Archivio personale" (kfpbb-gurkw)
[GNCGI] 15:42:55 INFO: Completed initial scan of sendreceive folder "Archivio studio" (pzsud-nnkxr)
[GNCGI] 15:43:01 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[GNCGI] 15:43:01 INFO: Detected 0 NAT services
[GNCGI] 15:43:07 INFO: Connection to LBZU575 at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: reading length: EOF
[GNCGI] 15:43:07 INFO: Established secure connection to LBZU575 at 192.168.1.129:57459-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:07 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:57459-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:13 INFO: Established secure connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:13 INFO: Replacing old connection 192.168.1.129:57459-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 with 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 for LBZU575
[GNCGI] 15:43:13 INFO: Connection to LBZU575 at 192.168.1.129:57459-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: replacing connection
[GNCGI] 15:43:13 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:23 INFO: Connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: reading length: read tcp 192.168.1.129:22000->192.168.1.10:22000: wsarecv: Connessione in corso interrotta forzatamente dall'host remoto.
[GNCGI] 15:43:23 INFO: Established secure connection to LBZU575 at 192.168.1.129:49585-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:23 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:49585-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:37 INFO: Established secure connection to LBZU575 at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:37 INFO: Replacing old connection 192.168.1.129:49585-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 with [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256 for LBZU575
[GNCGI] 15:43:37 INFO: Connection to LBZU575 at 192.168.1.129:49585-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256 closed: replacing connection
[GNCGI] 15:43:37 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:43:39 INFO: Connected to already connected device LBZU575 (existing: [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256 new: 192.168.1.129:64658-173.212.211.244:22608/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256)
[GNCGI] 15:43:43 INFO: Joined relay relay://213.109.162.234:22067
[GNCGI] 15:44:13 INFO: Established secure connection to LBZU575 at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
[GNCGI] 15:44:13 INFO: Replacing old connection [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256 with 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 for LBZU575
[GNCGI] 15:44:13 INFO: Connection to LBZU575 at [::]:22000-192.168.1.10:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256 closed: replacing connection
[GNCGI] 15:44:13 INFO: Device LBZU575 client is "syncthing v1.18.3" named "Nas" at 192.168.1.129:22000-192.168.1.10:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256
This Synctrayzor:
2021-10-23 11:24:52.4849 #12940 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 170MiB. Private Memory Size: 116MiB. GC Total Memory: 15MiB
2021-10-23 11:26:10.1703 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:26:10.1703 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:26:10.1703 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:26:10.1703 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:28:52.8490 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:28:52.8490 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:28:52.8490 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:28:52.8490 #12940 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2021-10-23 11:29:52.4869 #12940 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 170MiB. Private Memory Size: 116MiB. GC Total Memory: 16MiB
2021-10-23 11:34:52.4974 #12940 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 170MiB. Private Memory Size: 116MiB. GC Total Memory: 16MiB
2021-10-23 15:41:55.8649 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate directories in folder E:\System Volume Information
2021-10-23 15:41:55.8649 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate files in folder E:\System Volume Information
2021-10-23 15:41:56.8274 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate directories in folder D:\System Volume Information
2021-10-23 15:41:56.8274 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate files in folder D:\System Volume Information
2021-10-23 15:42:49.3302 #12940 [Info] SyncTrayzor.Syncthing.SyncthingProcessRunner: Starting syncthing: C:\Users\Workstation\AppData\Roaming\SyncTrayzor\syncthing.exe
2021-10-23 15:42:55.4230 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate directories in folder E:\System Volume Information
2021-10-23 15:42:55.4230 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate files in folder E:\System Volume Information
2021-10-23 15:42:55.4323 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate directories in folder E:\System Volume Information
2021-10-23 15:42:55.4323 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate files in folder E:\System Volume Information
2021-10-23 15:42:55.8289 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate directories in folder D:\System Volume Information
2021-10-23 15:42:55.8289 #12940 [Warn] SyncTrayzor.Services.Conflicts.ConflictFileManager: UnauthorizedAccessException when trying to enumerate files in folder D:\System Volume Information
2021-10-23 15:45:48.2344 #12940 [Info] SyncTrayzor.Services.MemoryUsageLogger: Working Set: 170MiB. Private Memory Size: 116MiB. GC Total Memory: 16MiB
There are two issues here.
Firstly, you are trying to sync drive roots (i.e. D:\ and E:\). There is a known issue at the moment, where file system watcher doesn’t work on drive root paths in Windows (see https://github.com/syncthing/syncthing/issues/7944). If you absolutely need to sync those paths, then I’d suggest using junctions/symlinks or mount points, and then pointing Syncthing at those instead (e.g. use the Disk Management to mount your D: and E: drives to something like C:\Mount\D and C:\Mount\E and then point Syncthing at the two).
Secondly, you really should add System Volume Information to your ignore patterns. This is a system folder that is specific to its partition and should never be synced. Of course, Syncthing will fail to even access it without being run as Administrator or SYSTEM, but still, your folders will be marked as having “failed items” all the time if you don’t ignore it.
1 Like
Has anyone confirmed that the watcher doesn’t work on root directories? That ticket sounds more like an issue related to a particular setup. At least the speculation about using incorrect paths (C: instead of C:\ are definitely false).
Yeah, I did a test on my system when that issue was first opened. It does not work indeed.
1 Like
Ok, I can try to move them from the root to a folder. I have to say that on the nas I use Docker, could be a problem?
I already added System Volume Information to the ignored patterns, this is my .stignore:
$RECYCLE.BIN
System Volume Information
$WINDOWS.~BT
pagefile.sys
desktop.ini
Is it right?
No idea about the NAS, but this problem is specific to Windows.
I’d say it looks fine. I usually add a little bit more though.
(?d)$recycle.bin
(?d)config.msi
(?d)desktop.ini
(?d)hiberfil.sys
(?d)mediaid.bin
(?d)pagefile.sys
(?d)swapfile.sys
(?d)system volume information
(?d)thumbs.db
(?d)windowsimagebackup
I followed your instructions and created a folder, in this way watcher work like a sharm. Next with Disk Management I crearted a mount to C:\Users\Workstation\Sync\D but watcher doesn’t work, same thing with symlink.
How about
mklink /j "C:\Users\Workstation\Sync\D" "D:\"
?
Of course, you can use mklink /d too, but that one requires to be run as Administrator, and there also are some security and functionality related differences between the two. I’d suggest mklink /j unless you actually need the other one.
I’m sorry for recommending the mount point path. I’ve just tested myself again, and indeed it doesn’t work either 
. Using a junction/symlink does the job though.
@imsodin I think it’s interesting that file watching doesn’t work when using mount points too, because it means the issue is really about drive root paths but not necessarily related to using drive letters (and their trailing backslash).
For the record, this is what mount points look on the disk,
Directory of C:\Mount
<JUNCTION> 4a6fe5e0-e13d-4eb7-bd21-528d95c8efe7 [\??\Volume{4a6fe5e0-e13d-4eb7-bd21-528d95c8efe7}\]
<JUNCTION> b7b3ce63-4662-4452-90ba-3a5869d7bab4 [\??\Volume{b7b3ce63-4662-4452-90ba-3a5869d7bab4}\]
<JUNCTION> ea6ad4c8-2599-417c-bb68-fc097f90de66 [\??\Volume{ea6ad4c8-2599-417c-bb68-fc097f90de66}\]
and pointing Syncthing at C:\Mount\4a6fe5e0-e13d-4eb7-bd21-528d95c8efe7 doesn’t work (in terms of file watching).
I edited my previous post. I used a wrong command but also symlink doesn’t work. Tomorrow I’ll test junction.
I tried also junction (mklink /j "C:\Users\Workstation\Sync\D" "D:\") but neither this work. Can you explain me please how did you get it work?
I solved the sync problem from root folders disabling Watch for Changes from local web interface and enabling directory watch in Synctrayzon app, I use v1.18.4-rc.1
You are right. My tests were flawed, because what I remembered as a junction to a drive root path actually linked to a subfolder in it. I have now redone all the testing using a fresh configuration. It doesn’t seem possible to have the file watcher working on drive root paths at all, regardless whether we’re using letters, mount points, or junctions/symlinks.
I’d say the SyncTrayzor internal file watcher is a valid (and only?) workaround in this case.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.