As we all know, Linux is case sensitive, so the file A.txt is different from a.txt. However, in Windows, A.txt and a.txt are the same. So, when I copy a file from Linux to Windows via CIFS, what is the outcome? Are there any scenarios where this could cause file system corruption on the Windows side?

No, because as you said, Windows is not case sensitive. No matter what case you use in the filename, Windows will treat it the same.

It is possible that myfile will overwrite MyFile at the windows end..

In the event that a linux cifs-shared directory contains two file that differ as above, the windows host will display their names correctly. When you try to copy the second to the same directory as you copieh the first - now they have to obey the rules of the windows native file-system... you'll either got a warning or the second file will get renamed.

In Windows, it is possible to have two files with the same nome in different directories. What happens if you try to copy them both to the same directory?

OT: There is a user wanting to contact slowcoder
Please visit this thred. Concerns possible license ambiguity in code written for iPodLinux.

Right. I understand how the Windows file system works. What I wasn't sure about was the correlation between Linux's CIFS and Windows file sharing. As in, maybe there is a miscommunication between the two. I had an incident where 2 similarly named files were copied through CIFS from Linux to Windows, and the Windows file system corrupted. I was thinking it's just an isolated corruption, but was trying to determine what the cause was.

P.S. I responded to the other thread referring to ipodlinux. Wrong SlowCoder; I apparently have multiple personalities . But thanks for letting me know.

The corruption would be unrelated. (If this behavior actually did corrupt the fs, then Windows is even worse than everybody already thinks...)No worries - obviously your evil twin: you would never leave a license ambiguous