Shadark

Just a bit more info, it's not a problem anymore for me (I managed to explore the filesystem using subprocess.run with the find command and I got correctly the filenames, so I could run everything just fine. Still, files (not only folders, even files) appear similarly as 0b files, 1970 creation date, numerical location and obviously no extension recognized, since everything after the pipe character | gets truncated. Not sure if I should move this topic (or recreate it) in the bug report section? So far I couldn't find this problem anywhere.

Ok, I didn't realize that I could enter the folders escaping the pipe character when doing cd, I can also delete the files and folders. When doing ls the last modified date appears correctly, so could it be an Unraid WebUI issue instead? (Besides the wrong characters when using os.listdir in Python, that's a whole another matter I guess)

(First of all, sorry for any grammatical mistakes, English isn't my first language!) Hi, I've been using Unraid 6.11.5 for a few days, configuring a new NAS and overall enjoying my experience. I've also set up a Torrent client using the Apps section (qBittorrent). It's also relevant that I was trying to configure a folder where I would leave .torrent files (from my Windows computer) and then qBittorrent would watch that folder and start downloading any torrent in there. What I found is that, when some of the files in the Torrent contain the character '|' (pipe), things start to break. In qBittorrent everything seems to be fine, torrents are downloading, all characters appear (both in the torrent name and in the list of contents), etc. However, I was getting some strange results around. The first was that using a SMB connection to the download folder from my Windows PC, folder names appeared weird for some folders (the ones with | in them). They appear as '·' or a different character. I found this when exploring the path using a Python script to match folder names to torrent names, the torrents would appear fine but the folder names would contain something like: 'something \uf027 something' and obviously they didn't match. I thought that maybe the pipe character was breaking things since, you know, it's Unix and all. I went to check the folders in the disk view using the WebUI and it's even weirder: The folders with a last modified 1970 date and a location with numbers are not explorable, if I try to click one of them I get sent back to root (/), but the tooltip that shows my current path (Index of [...]) still shows as if I was exploring the folder. Also, the folder names are truncated after where the pipe character would've been. Finally, I've been trying to delete those folders but it doesn't seem to work, at least from the console. rm -rf folder_name does nothing. I was originally trying to solve the whole torrent <-> files match, but now I would be happy to just solve the issue of these folders. I'm attaching diagnostics file in case it's useful. Thanks in advance!clovisbray-diagnostics-20230409-1633.zip