Issue:
When copying a batch of files from an Ubuntu SAMBA share to a local windows drive; if files with identical names, but different cases, eg; 'FILE.txt' and 'file.txt', are being copied, you are prompted to overwrite / skip the 'duplicate' files, but either option results in the existing file being deleted and the rest of the copy job being cancelled or skipped.
Issue Severity: Moderate (Issue can cause premature cancellation of large batch copy jobs)
Additional information:
Repeating the same action using Windows Explorer results in expected behavior (ie; the file is overwritten or skipped and the copy continues)
I have not tested other versions of Ubuntu or Linux
Environment:
Win 7 x64
Opus v10.2.0.0 x64
Ubuntu 12.04
IMO, it's a bug (or mis-configuration) in Samba if it even allows two files with the same name (ignoring case) to appear in the same directory. Samba is meant to emulate a Win32 network share and this is an impossible situation for one to be in. One file should hide the other (or have its name changed on-the-fly so the two names do not conflict, or some other scheme).
If we can recreate this locally then we might be able to improve how Opus reacts to it, but we're talking about something that shouldn't happen in the first place and which is inherently problematic. It's something that should really be avoided on the Linux/Samba side, since you can't copy all the files anyway.
I have two files in my test samba share, "One.txt" - 224 bytes, and "one.txt" - 167 bytes.
When I double-click "One.txt" (224 bytes), the contents of "one.txt" (167 bytes) are opened. This happens in Explorer as well as Opus.
So it seems that although Samba is preserving case sensitivity in directory listings, it is doing non-case sensitive resolution when asked to open files.
I can confirm the same behavior on my system. However, there must be a way around this issue in terms of file copying as Explorer handles it as expected.
It seems to either be intermittent or related to when the files were created, as after I rebooted the VM the problem seemed to go away. It then came back again when I created a third file.
Anyway when the server actually does return the right file, I can't get this to fail in Opus. Copying files seems to work just as well as in Explorer. I wonder if it was this intermittent name resolution issue that caused the symptoms you described?
Hmm, it happened to me a number of times after reboots. In any case, I acknowledge that you aren't able to reproduce this so we'll leave it at that for now. I tried to reproduce the issue again with new files (I deleted the old ones, somewhat foolishly in hindsight), but I can't reproduce the same behavior again either.
Rebooting doesn't seem to be 100% the trigger to make it stop happening FWIW; it just seems quite unpredictable. Maybe Samba has options that can force it to always do case-sensitive name resolution? If so that would probably fix it.