Copying exported library fails: “colons” in directory names conflicts with SMB

Hi,

I wanted to make a bug/Issue report on kodi guthub, but there is suprisingly no “Issues” section :/.

I’m not sure whether this is a kodi related or a LibreELEC related issue, but as KODI is responsible for creating the library it might likely be a KODI issue rather than LibreELEC:

When I export the video library (single file) to SD Card (ext 4) on my Odroid C2 everything is fine at first. If you then try to copy this directory – which contains fanart, coverart and so on of tv shows and movies – this fails. It fails via SMB, but I’m not sure if this affects also NFS or so. The same happens if I export the Library to my external NTFS USB drive.

The issue is that some library directories have names like:

TRON:_Der_Aufstand

This is only one of at least 10 directories which have colons in its filenames, thus I cannot copy the Backup off the system to another system.
As filenames containing a colon are not allowed on NTFS and in windows (are they allowed on ext4 drives?), this behavior damages the filesystem on my NTFS HDD (connected to Odroid C2 running LibreELEC). At first I didn’t notice it, because the directories were build during library export process on my SD-Card. But when I connected to the drive via SMB and tried to copy the backup before formatting the SD-Card, it was not possible. And it is also not possible to rename these directories :/. Also I can only get rid of this directories if I format the drive (NTFS drive with 3TB of data).

Later I noticed this:
The faulty directories are there directly after exporting… I can see them in Kodi file manager and via SMB. But I get an error if I try to access them via SMB. But then suddenly when I connect this usb-device again to my windows Laptop afterwards, these directories are missing, I’m not sure what happens to them. Also a lot of other directories were not there anymore. I assume that all directories, which were written after the faulty one (containing this colon), are broken then and not visible or corrupted. I’m not sure if they occupy space on the disk, but I think they do, even though they cannot be accessed or found anymore, but they could be seen at first before reconnect.

The result of this is: The library backup (export) is broken immediately after doing the export because those colon-library entries are gone and some other folders which were written afterwards are also gone.

All this sounds a bit confusing (colon directories there at first, but not accessable and not deletable; then gone completely and taking other folders with them), but something strange is happening because of these colons in filenames, which should be avoided during creation of library (and backup) in the first place.