So… I make a quick look at what can I find inside System.IO, and Path.GetInvalidPathChars() and Path.GetInvalidFileNameChars() – it seemed that those functions will help me find those files and directories that contains illegal characters. Boy… I was wrong ;)
At the beginning I wrote a very simple program (C#) that recursively traversed through all FileSystemInfo objects (using GetDirectories() and GetFiles() methods) present in a given directory. The problem was, that when GetFiles() method was invoked inside a directory that contained files with illegal characters – program crashed (“Illegal Argument Exception”). I couldn’t understand it. I know what was the directory that caused problem and I easily found a file that was a cause of all this mess. The file name contained a pipe “|” character that is not allowed (at least on Microsoft’s systems).
I wondered how should I change my small utility to make it able to find all illegal files and generate a cute report at the end instead of crashing. I could see the file using Total Commander, Windows Explorer and even dir command executed within cmd.exe. I could – however – copy the file, rename it (tried bazylion of different approaches to achieve this task – using Universal Naming Convention didn’t help a bit). I decided to rewrite main part of my utility and to use System.Diagnostics.Process and output of “DIR /A-D /B” for files and “DIR /A:D /B” for directories. My idea was to not checking the names of FileSystemInfo objects that I can get without problems using GetFiles and GetDirectories methods. I assumed (and I hope that it is assumption is correct) that if information about a file or directory can be get, than there is no problem with this object. So I decided that my code should now look more like this:
try
{
FileInfo[] files = root.GetFiles();
}
catch (System.UnauthorizedAccessException)
{
}
catch
{
GetSystemEntries(root, EntryType.File);
}
In the function that traverses through all the object there is another similar block of code that does similar task but for directories. I wasn’t sure if this approach is ok – exception catching influences performance, but it didn’t take more time than SyncToy to look through all my drive (so I assume that the performance is acceptable). GetSystemEntries is a function written by me, that invokes dir command in specified directory looking for files or directories, and analyzes output (checks if there are any invalid characters in file or directory name).
Yup, one problem resolved. But what about the file? As far as I remember, it was created by a browser (saving page) and it’s name comes from the title of the page, which was divided in sections using pipes. The funny thing (for me) is that I can not understand how OS may actually allow anyone to create a file with invalid characters in name (I suppose this file was created by Mozilla Firefox 3.0x). I have spent a lot more time looking for a solution how to delete the file, rename it, or do whatever to make it a file with a valid name. Back in the old dos-command-prompt days I used several times a great tool by Norton – diskedit.com – it was very powerful disk editor, that saved me a couple of times. But… although I found some similar tools, I was a bit too afraid to use them. NTFS is much more complicated than good-old FAT, and I really didn’t want to lose all my data. I rebooted to Ubuntu, and tried renaming. It worked. Then I tried to remove the file. No problems. So… thank you Cannonical :)
]]>