Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

623

July 28th, 2014 16:00

EMCopy Problem

I'm having an issue where it appears that the /xf switch is not working.  I've created a simple directory structure that I can use for testing emcopy so that I can make sure that I fully understand its behavior before using it in production

I'm using the following command: emcopy64 d:\test1 d:\test2 /xf file1.txt /s /d

When I run it, it shows "Excluded File: file1.txt" but yet the file is copied from the folder test1 to test2

What gives??  Any suggestions?

Thanks,

Lamar

4 Posts

July 28th, 2014 16:00

Well, I think I figured out the problem.  It appears that the stinker (emcopy) is case sensitive (e.g. file1.txt is not equal to File1.txt).  So even though Windows doesn't care about case, emcopy sure does.

It would be nice if a switch were added to turn OFF case sensitivity.  I guess I can see why case sensitivity is there, for those who may be copying Linux or Mac file structures who have case sensitivity turned on.  So, again, it would be nice to have a switch to set case sensitivity in emcopy

4 Operator

 • 

8.6K Posts

July 29th, 2014 03:00

That makes sense – even though CIFS isn’t case sensitive the file system is case preserving

3 Apprentice

 • 

1.2K Posts

July 29th, 2014 08:00

In previous migrations, I've created a file with a list of excluded filenames, which included different cases, such as file1.txt File1.txt and FILE1.txt.  You can get Windows to expand the contents of this file, after the /XF flag, so that you can get a pile of filenames easily on the command line.  Yes, it's pretty crude, but it's handy in a pinch!

Hope this helps!

Karl

No Events found!

Top