Trailing dot / period causes havoc (TailCharacterConflict)

Files with trailing dot (period, full stop) like “file 2020.01.01.” or directories cause a real mess when there are Linux and Windows machines within the share. (Discussed earlier at Unable to sync documents or files ending with period(.) symbol)

It seems that Linux sharing such a file somehow gets (or got) created on Windows, but they cannot be used (deleted, updated) after by “usual means”. It seems to be posisble to delete them by manual intervention; however Syncthing seems to fail deleting them. The mess starts when syncthing actually starts reading it back and redistribute them.


We had a share with a such filename created a long time ago (possibly back then Syncthing wasn’t aware of the problem), and it was unmanageable at Windows. When we have realised that last week I tried to delete it on Linux. It has been deleted, also deletion distributed.

However since Windows cannot delete it the directory was still there, then syncthing finds it again at the next scan, it will reappear everywhere, even after some Windows user manually deleted their files, since other windows users still had the file. Then it may start to create conflicted files, but when the directory have trailing dot these files may will be created in the directory with the wrong name.


I believe windows versions shall emit an error when someone tries to share such a file from Windows (and reject sharing it), and I would guess that Windows version does already reject receiving (creating) such files with the TailCharacterConflict trailing error, which is also a good way to handle it (or it shall it is doesn’t).

If it’s a valid concern feel free to create a real issue from it; if it’s not your comments about why are welcome. :slight_smile:

Yeah we added this check sometime in 2020, but only on the “incoming” side, it was never anticipated that the invalid filenames would originate on disk. That said, even if they do they would be rejected by the other side – if it’s v1.11.0 or newer.

v1.22.2 sends it back right now with RemoteChangeDetected. :slightly_frowning_face:

A Linux box will do that, yes, but not Windows?

I was lead to believe it’s windows, but I will ask about it again. Version number doesn’t tell me on my end.

In any case, modern Syncthing won’t help you get rid of this if your Windows boxes are already “infected”. :confused: Whether it’s worth it to also try to filter this out on the local side, in order to avoid announcing it to other devices, I’m not sure.

I’ll keep you posted when people are back from Jesus’ and the Gregorian Calendar’s parties. :wink:

1 Like

The machine re-introducing the file (it is unable to delete) is „Windows 10 Enterprise”.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.