WD MyCloud silently remaps special Windows filenames (com1, etc.),
even if the filename has an extension (com1.txt, etc.).
Microsoft suggests avoiding the following reserved names
(see https://msdn.microsoft.com/en-us/library/aa365247.aspx):
aux com1 com2 com3 com4 com5 com6 com7 com8 com9 con lpt1 lpt2 lpt3 lpt4 lpt5 lpt6 lpt7 lpt8 lpt9 nul prn
plus those names immediately followed by an extension.
On MyCloud, filenames com[5-9] and lpt[4-9] work as expected,
aux com[1-4] lpt[1-3] nul prn are mangled,
and con does not work at all.
Host: MacAir running OSX 10.6.8.
WD MyCloud 2TB, firmware 4.01.02-417.
Create com1.txt and con.txt on host filesystem:
steve@macair ~: cd tmp
steve@macair ~/tmp: date >com1.txt
steve@macair ~/tmp: cat com1.txt
Sat Feb 7 23:49:36 PST 2015
steve@macair ~/tmp: date >con.txt
steve@macair ~/tmp: cat con.txt
Sat Feb 7 23:49:43 PST 2015
The same commands fail on MyCloud share wd2000:
steve@macair ~/tmp: cd /Volumes/wd2000/test2
steve@macair /Volumes/wd2000/test2: ls
steve@macair /Volumes/wd2000/test2: date >com1.txt
steve@macair /Volumes/wd2000/test2: ls
CR23RR~9.TXT
steve@macair /Volumes/wd2000/test2: cat com1.txt
cat: com1.txt: No such file or directory
steve@macair /Volumes/wd2000/test2: date >con.txt
-bash: con.txt: File name too long
The created file for com1.txt is CR23RR~9.TXT,
and con.txt file creation simply fails.
Frankly, this is beyond belief.
