|
|
|
A beautiful filename, 251 char long
A customer of us recently complained that he couldn’t find a specific file, even when searching for word that he knows was in it. This is’t a total uncommon question. Sometime the user don’t have permission to the file, or the location is’t indexed yet or some other problem. So our cto Runar Buvik asked what the name of the file was, so he could take a look.
- It’s Protocol_Amending_the_Agreements_Conventions_and_Protocols_on_Narcotic_Drugs _concluded_at_The_Hague_on_23_January_1912_at_Geneva_on_11_February_1925_and_19 _February_1925_and_13_July_1931_at_Bangkok_on_27_November_1931_and_at_Geneva_ on_26_June_1936.doc. Yes, the name was in fact “Protocol_Amending_the_Agreements_Conventions_and_Protocols _on_Narcotic_Drugs_concluded_at_The_Hague_on_23_January_1912_at_Geneva_on_11_ February_1925_and_19 _February_1925_and_13_July_1931_at_Bangkok_on_27_November_ 1931_and_at_Geneva_on_26_June_1936.doc “. That 251 characters long! After some investigation it turned out that the underlying filesystem, ntfs, allow filename as long as 255 characters, but Windows refused to serve this file by SMB. Instead we got a “No such file or directory” error, even if opening the folder as a network share in Windows Explorer and clicking on the file. There actual is such a treaty name according to Wikipedia, but that dos’t mean that the file need to be named the same. Please keep you filenames below 128 characters people, or you will be in trouble sooner or later! Bdw, The ES supports filenames up to1024 characters. Longer then that, and is’t probably just noise anyway. CommentsLeave a Comment |
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||