Junction Folders not syncing anymore

syncthinguser123 · October 25, 2024, 9:24am

I have used the function “junctionsAsDirs” for a long time and now (maybe because a recent update) the function is no longer working anymore. It doesn’t detect these folders anymore. And syncthing also tells me something about “local changes” which I never did. Why is it now doing all this? I really don’t want to switch to another software, because it really worked great until now. I couldn’t find anything useful in the log file, but I could send it to the devs if needed. Running Version v1.28.0, Windows (64-bit Intel/AMD) “Gold Grasshopper” - Build 2024-10-04 on both devices

tomasz86 · October 25, 2024, 9:51am

Known issue:

github.com/syncthing/syncthing

Junctions as dirs doesn't work anymore

opened 08:11PM - 18 Oct 24 UTC

hardtopnet

bug needs-triage

### What happened? I used to be able to sync the contents of NTFS junction di…rectories. I recently noticed that it doesn't seem to work anymore. I tried on 2 different machines, one with admin/systemwide install, the other with user install. On the systemwide install I added SyncthingServiceAcct to the perms on the sync'ed folder. The _Junctions as dirs_ option is set. Relevant logs below. Here are some screenshots: ![syncthing_main](https://github.com/user-attachments/assets/9f85bbd5-fcfe-4494-a186-c336cecf9eda) ![files](https://github.com/user-attachments/assets/b4e08b5f-5321-4fba-95df-5c453097abb1) ![options](https://github.com/user-attachments/assets/71523094-7113-4494-bc43-eae9b4ab9331) ![perms](https://github.com/user-attachments/assets/94928024-32a6-4fb2-a863-ff559e66db9a) ### Syncthing version v1.28.0 ### Platform & operating system Windows 10 Pro x64 ### Browser version Brave Browser 1.71.114 ### Relevant log output 2024-10-18 22:21:00 casefs.go:255 basic c:\aaa\junction Stat . {0xc00013c070} <nil> 2024-10-18 22:21:00 casefs.go:255 basic c:\aaa\junction Stat .stfolder {0xc00013c230} <nil> 2024-10-18 22:21:00 casefs.go:479 basic c:\aaa\junction DirNames . [.stfolder file junctiontotarget] <nil> 2024-10-18 22:21:00 logfs.go:173 basic C:\ProgramData\Syncthing\index-v0.14.0.db Usage . {702322937856 999533756416} <nil> 2024-10-18 22:21:00 log 40 StateChanged map[duration:182.8508201 folder:dayss-x9hqe from:idle to:scan-waiting] 2024-10-18 22:21:00 walker/dayss-x9hqe@0xc0000e76b0 Walk [] Matcher/[]@0xc0002422d0 2024-10-18 22:21:00 log 41 StateChanged map[duration:0.8508201 folder:dayss-x9hqe from:scan-waiting to:scanning] 2024-10-18 22:21:00 walk: path=. 2024-10-18 22:21:00 ancestorDirList: Contains 'junction' 2024-10-18 22:21:00 ancestorDirList: Push 'junction' 2024-10-18 22:21:00 walk: path=.stfolder 2024-10-18 22:21:00 walker/dayss-x9hqe@0xc0000e76b0 ignored (internal): .stfolder 2024-10-18 22:21:00 walk: path=file 2024-10-18 22:21:00 walker/dayss-x9hqe@0xc0000e76b0 checking: File{Name:"file", Sequence:0, Permissions:0644, ModTime:2024-10-18 21:11:45.2540096 +0200 CEST, Version:{[{62S6MDD 1729282860}]}, VersionHash:, Length:7, Deleted:false, Invalid:false, LocalFlags:0x0, NoPermissions:false, BlockSize:131072, NumBlocks:0, BlocksHash:, Platform:{<nil> <nil> <nil> <nil> <nil> <nil>}, InodeChangeTime:1970-01-01 01:00:00 +0100 CET} 2024-10-18 22:21:00 walker/dayss-x9hqe@0xc0000e76b0 unchanged: File{Name:"file", Sequence:1, Permissions:0644, ModTime:2024-10-18 21:11:45.2540096 +0200 CEST, Version:{[{62S6MDD 1729282860}]}, VersionHash:, Length:7, Deleted:false, Invalid:false, LocalFlags:0x0, NoPermissions:false, BlockSize:131072, NumBlocks:1, BlocksHash:d3535c46046caa8f282f78819d9f8616010eacd1d507e952c833a67ada965799, Platform:{<nil> <nil> <nil> <nil> <nil> <nil>}, InodeChangeTime:1970-01-01 01:00:00 +0100 CET} 2024-10-18 22:21:00 walk: path=junctiontotarget 2024-10-18 22:21:00 ancestorDirList: Pop 'junction' 2024-10-18 22:21:00 log 42 StateChanged map[duration:0.8525193 folder:dayss-x9hqe from:scanning to:idle]

If you rely on this functionality, I’d recommend disabling upgrades for now (e.g. see https://docs.syncthing.net/users/config.html#config-option-options.autoupgradeintervalh), then manually downgrading to Syncthing v1.27.12.

syncthinguser123 · October 25, 2024, 10:18am

Ok, now I also got the message that I have some “local changes” over 2 GB so it’s not just some “thumbs.db” or similar. But I can’t remember doing such thing. Is this related to that issue? I just saw that this “folder” that I sync doesn’t use any junctions.

tomasz86 · October 25, 2024, 10:44am

You may want to post a screenshot showing the error at hand. However, the issue related to junctions, which I’ve also confirmed in my testing, simply makes Syncthing not see them at all.

syncthinguser123 · October 25, 2024, 10:58am

I don’t think the “local changes” warning message is related to the junction thing. I still need to look closer into this, as I’m still not 100% certain that I really did this.

syncthinguser123 · October 25, 2024, 12:11pm

It just was me, who did the “local changes”, so it’s definitely not related to that issue. I downgraded to version v1.27.12. and now everything works again.