Often, when I delete folders, the root and some random subfolders wont be deleted and produce directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix). The reference to the ignored files does not make sense to me, as the folders do not match the ignore patterns. For instance:, here I deleted ~25 folders, but deletion of this seemly random subset did not propagate to the st-server on my NAS:
Deleted folders:
The following items could not be synchronized. They are retried automatically and will be synced when the error is resolved.
projects/2021_swiss_invertebrates/dubendorf_ponds directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
syncing: delete dir: directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
projects/2021_swiss_invertebrates/dubendorf_ponds/Benthos_1A_Dreis_140619 directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
projects/2021_swiss_invertebrates/dubendorf_ponds/Benthos_3D_Macro_140619 directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
projects/2021_swiss_invertebrates/dubendorf_ponds/October_2019 directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
projects/2021_swiss_invertebrates/dubendorf_ponds/October_2019/Benthos_1B_Contr_28.10.19 directory has been deleted on a remote device but contains ignored files (see ignore documentation for (?d) prefix)
And this is my ignore pattern (via #include stglobalignore):
Are you sure? Those are hidden files, so you might have missed them. Syncthing only throws this error when scanning the directory to be deleted and finding a file.
I had similar problems with elements that originally came from other platforms (Windows) on my Synology servers and also such directories could not be completely deleted via Syncthing. Therefore, I have included such elements in folder Ignorelist:
Have you verified that using something like ls -lah in the terminal?
Because I don’t trust file managers provided by these funky NAS platforms. They choose to create crazy @ea et al directories, and then pretend they don’t exist by hiding them in the file manager, when they clearly do exist.
It is true that the @eaDir are a veritable plague in the Synology´s filesystem. If you access a Synology with the terminal under root, there are some directories in the root directory that begin with @.
However, these are directories that are not seen by the “normal” file system or by Syncthing. These are not individual files and are out of the question here. In the file system, these @eaDir directories are usually located in each root directory of the shared folder if its structure contains images, but usually not in the substructures.
Finally it is a good idea to use the terminal to check what is in the relevant directories.