@eaDir not being ignored with ignore pattern

[JoeWpi (Joe)]

Hello, I’ve been searching reddit github and on here for answers seeing this issue goes back for years but haven’t seen a real solution. I have 5 computers using syncthing, and I recently just added a synology NAS to sync with all of them. The NAS is now adding a “@eaDir” folder inside of every folder and its causing my projects to get very busy.

I have tried:

(?i)(?d)**.pmxignore
(?i)(?d)**.DS_Store
(?i)(?d)**.Trash
(?i)(?d)**.DeletedFiles
(?i)(?d)**.stignore
(?i)(?d)**folder/@eaDir

and

(?i)(?d)**.pmxignore
(?i)(?d)**.DS_Store
(?i)(?d)**.Trash
(?i)(?d)**.DeletedFiles
(?i)(?d)**.stignore
(?i)(?d)**@eaDir

How can I filter this out so that syncthing actually ignores these files & Folders that the NAS is creating?

[JoeWpi (Joe)]

Actually, I’m just noticing now that the “.DS_Store” files are not being ignored either and are still syncing, even though as mentioned above they are inculded on the .stignore file to be ignored. Whats going wrong here?

[calmh (Jakob Borg)]

Just

@eaDir

should be sufficient. Of the top of my head I’m not sure what the result is with the double star at the front, but at the very least it’s not required.

[JoeWpi (Joe)]

The double asterisk says its “Multi level wildcard (matches multiple directory levels)” Thats just how the previous guys set it up so I didn’t question it. But, either way, it doesn’t seem to be filtering

[tomasz86]

How are you editing the ignore patterns? In the Syncthing Web GUI on Synology? Can you post a screenshot?

[JoeWpi (Joe)]

I’ve been editing it through the web GUI yes,

Here it also is just in the .stignore file:

[tomasz86]

This looks like you’re editing on the Windows side. You need to either add the patterns on all devices or just on Synology. Please keep in mind that this won’t delete the existing files that have already been synced. Those you need to remove manually.

[JoeWpi (Joe)]

Okay, I have edited the ignore pattern on all devices and manually deleted the @eaDir folders.

Nothing has popped up just as yet, but I’m not sure how to trigger Synology to make another @eaDir folder to test.

[tomasz86]

You can just create a folder named @eaDir anywhere manually, then rescan the folder in the GUI and see whether the local state has changed or not.

[JoeWpi (Joe)]

Thanks @tomasz86 I guess I just assumed it wasn’t working because it wasn’t removing the already synced folders. Since I added the ignore pattern to all machines, and manually removed the current “@eaDir” folder, the issue seems resolved.

I manually created a @eaDir folder on one of the computers, and it did not seem to sync up with anything else.

Thanks again!