Guys,

 

I have been troubleshooting a problem for about 2 weeks and I finally know what the cause of my problem is. unRAID HATES special characters. I have a script that checks each file sent to my server against an SFV file for integrity and creates empty folders and symlinks when a folder is incomplete. For example, if I am downloading a Pearl Jam cd, and track 8 of 10 is missing, it will create a folder saying it is 90% complete with a little progress bar of #'s in the CD directory and a symlink up a level saying (incomplete)-Folder_name that links to the Pearl Jam CD, in this example. If and when all files are verified, a complete folder is created in the CD dir.

 

My problem is, the symlink nor the progress bar are being created and Ive narrowed the problem down unRAID not allowing these characters. I realize these characters have different meanings, but these are only temporary files. The complete folders are being created and working fine. Is there any way I can override this character rule to allow these characters?

 

When you say "special characters" - do you mean accented characters?  Asian characters such as Chinese?

 

I have loads of files with various accented, Chinese and Japanese folder names and file names which are stored quite happily on unRAID 4.7 and 5.0beta14 and which I can read and write as needed.  I doubt that the problem that you are seeing lies directly with unRAID.

Not accented characters, unRAID seems to not like the ! @ # $ % ^ & * ( ) _ | / \ [ ] { } characters in directory/file names.

 

Is there an exclude these characters setting somewhere I can alter? I sure hope so.

 

Here is an example:

 

Folder:

[#############:] -  95% Complete - (Rock) [sitename]

 

Symlink: up one level from the above folder.

(incomplete)-The_Animals-Retrospective-2004

 

Once something is done it creates these:

[sitename] - ( 135M 26F - COMPLETE - Punk Rock 2009 ) - [sitename]

From the information you posted it looks like the problem is with the script and not with the name or characters in the name being supported. 

Check the code that is creating the folder/symlink, I think it is the problem and not the name.

 

If you try to create an example folder using your example at the command line on your server, you'll see that there is no problem with using that name.

 

Try these examples:

 

mkdir "[www.sitename.com:] - 95% Complete - (Rock) [www.sitename.com]"

mkdir [www.sitename.com:]\ -\ 95%\ Complete\ -\ \(Rock\)\ [www.sitename.com]

 

ln -s DIRNAME/[www.sitename.com:]\ -\ 95%\ Complete\ -\ \(Rock\)\ [www.sitename.com] ../\(incomplete\)-The_Animals-2004

 

replace DIRNAME with the correct dirname for your file.

 

If it works at the command line, then the problem is with the script.

 

Greg

Thanks Greg for the reply.

 

I will try this in a few hours and post the results here, though I know it isnt an issue with the script. If I unmount the unRAID share and run the script on the local drives it works like a charm.

 

I will though try your suggestions and post the results here in a little bit.

 

As always, thanks everyone for your help.

 

Casey

Not accented characters, unRAID seems to not like the ! @ # $ % ^ & * ( ) _ | / \ [ ] { } characters in directory/file names.

In linux there are ONLY two characters that are not legal as part of a file name.  The NULL character, and the "/"

The "/" is used to separate directories in path to a file, so it cannot be used in a file or directory name.

 

 

Other than those two characters, any other is legal.

There are MANY characters that are NOT legal in MS-WINDOWS file names and paths.

 

There are MANY characters that have a special meaning to the "bash" shell in linux, and if UN-escaped, or left UN-quoted will be interpreted by the shell and expanded as appropriate.