March 31, 201610 yr Hi, I updated to Unraid 6 recently and noticed some folders having one or two unnamed files and folders within Windows. For example, I have a folder with episodes of a tv show and there is a file in the folder that is a blank page icon, has no named but has a filesize similar to the episodes. In another folder, the listing has two blank entries like this except they have folder icons. Trying to open one of these blank folders relists the same directory but adds another \ to the end of the path. These oddities don't show up when running ls -al over ssh. I feel like Samba isn't exporting the listing properly. Any ideas? Thanks.
March 31, 201610 yr Community Expert They have invalid characters in their name as far as Windows or SMB are concerned. Windows display a timestamp for them but can't display the file or folder name. You can go into Midnight Commander and sort on timestamp to find them and then rename.
March 31, 201610 yr Author You're right. That appears to be the case. I don't understand though why this wasn't a problem with v5 but is not in v6. Maybe now it's exporting characters WIndows can't read while the previous version didn't? Edit: I just read that Samba can apparently mangle names it can't properly export so Windows can read them. I would bet several of my files had been mangled in this way previously but no longer are with v6. Does this sound reasonable?
March 31, 201610 yr Community Expert You're right. That appears to be the case. I don't understand though why this wasn't a problem with v5 but is not in v6. Maybe now it's exporting characters WIndows can't read while the previous version didn't? Edit: I just read that Samba can apparently mangle names it can't properly export so Windows can read them. I would bet several of my files had been mangled in this way previously but no longer are with v6. Does this sound reasonable? You've got so many no's and not's in there that it sounds as if you don't have a problem now on v6 and you didn't have one before on v5. When I had this problem it was due to downloaded files, which had been named by someone else using a different language and character set. Maybe you just didn't notice it before.
April 8, 201610 yr Author You're right. That appears to be the case. I don't understand though why this wasn't a problem with v5 but is not in v6. Maybe now it's exporting characters WIndows can't read while the previous version didn't? Edit: I just read that Samba can apparently mangle names it can't properly export so Windows can read them. I would bet several of my files had been mangled in this way previously but no longer are with v6. Does this sound reasonable? You've got so many no's and not's in there that it sounds as if you don't have a problem now on v6 and you didn't have one before on v5. When I had this problem it was due to downloaded files, which had been named by someone else using a different language and character set. Maybe you just didn't notice it before. Sorry, I didn't realise I had a typo in there. I meant to say this wasn't a problem in v5 but is in v6. It looks like samba has functionality to mangle names of files it can't properly export. This allows Windows to see a file with a garbled name rather than seeing nothing at all. It seems to me that this feature was enabled in v5 and has been left out in v6. I dare call this an oversight.
Archived
This topic is now archived and is closed to further replies.