"File name too long" question?

[Northern Lawn]

When I transfer a large folder full of music or audio books between HD's (I do this for back up purposes) I'll get this message at the end saying a large number of files have to long a name for their destination. Then it will go on to list every one of them.

Recently I pulled over my audio book folder, something like 350 gigs, and I got about 47 of these messages. So I'm thinking widows won't allow them to transfer so I'm literally not backing up 100% of my files.

Is there a solution to this? Can I set windows 7 to allow any length file names?

 

[RebateMonger]

You need to fix the problem. Can you lose some of the upper-level directories? Or rename them to be shorter?

You can also Map lower level folders to drive letters and copy files using the mapped drive letters.

 

[seemingly random]

I assume you realize that the name length max includes folder names, name separators and drive letters and/or volume names. Sometimes this problem is fixed by simply shortening folder names near the root.

I've had a couple of occurrences of this where I've counted and the total length was less than the max. It might actually be a unicode character that's confusing things. I've always wondered how a directory structure that exists on a windows nfs volume with no apparent difficulty can contain some names that are too long when the explorer is directed to copy it to another nfs volume.

 

[Northern Lawn]

Originally posted by: RebateMonger
You need to fix the problem. Can you lose some of the upper-level directories? Or rename them to be shorter?

You can also Map lower level folders to drive letters and copy files using the mapped drive letters.

Not sure what Upper-level directories are but I think I could lose them

Any idea how?

 

[RebateMonger]

Originally posted by: seemingly random
I've always wondered how a directory structure that exists on a windows nfs volume with no apparent difficulty can contain some names that are too long when the explorer is directed to copy it to another nfs volume.

Yeah. Explorer has special issues with "long" names. When I HAVE to move files, no matter what, I use Microosft's RoboCopy utility. It'll copy files/paths that Explorer finds totally innaccessible.

 

[RadiclDreamer]

They also make a robocopy gui now for those that shy away from the command line

http://technet.microsoft.com/e....utilityspotlight.aspx

 

[Northern Lawn]

Originally posted by: RadiclDreamer
They also make a robocopy gui now for those that shy away from the command line

http://technet.microsoft.com/e....utilityspotlight.aspx

Ok I got that program but after I selected the source and destination, the Start copying button was still greyed out but I pressed F5 to make it start and a cmd window opened up and another window that said Failed.

Maybe it's not compatible with windows 7?

 

[RebateMonger]

RoboCopy for Windows 7 is included in Win7. Just try that one. You'll get used to the Command Line....eventually.

Just remember that RoboCopy is made to work with FOLDERS and not FILES. If you read the Robocopy /? section and an article or two, you'll get how it's used.

 

[Northern Lawn]

I keep getting a Invalid Parameter error. on the destination.

I'm trying to copy a 350 gig file from d: to c:

This is they command I'm using "robocopy /mir d:\audio books c:\desktop". (I've actually tried a variety of destinations I even went c:\users\mike\desktop I've also made a folder specific for this down load in the highest c directory but always the same error.

Any Idea what I'm doing wrong? I think I'm following their instruction to the tee. The /mir thing I've put 2nd and on the end that doesn't seem to matter so I don't know. It's just the destination that gets the error. I even started the cmd window with Run as administrator.

 

[RebateMonger]

You probably can't do a /MIR from a directory to another directory with a different name, since Robocopy will try to delete directories that don't exist on both ends. I'd be REALLY careful with the /MIR command and play only with "practice" folders.

/MIR goes on the END of the command.

Have you tried a simple "Robocopy source destination" yet? The /MIR option doesn't really seem appropriate for your needs.

 

[Northern Lawn]

I got it. This is an AWESOME program and seems so much faster then the drag and drop I used to do...

I did the straight copy you suggested (and I used a non relevant folder just in case) it didn't work as expected. It dumped all the contents on my desktop rather then bring them in the folder itself. It also ignore all the subfolders inside, which was most of the content.

But I made a folder on my desktop and made THAT the destination and I added a "/s" on the end and it reproduced the entire contents including all sub folders, real fast too.

Thanks so much.

 

[JuliaBrin]

When I transfer a large folder full of music or audio books between HD's (I do this for back up purposes) I'll get this message at the end saying a large number of files have to long a name for their destination. Then it will go on to list every one of them.

Recently I pulled over my audio book folder, something like 350 gigs, and I got about 47 of these messages. So I'm thinking widows won't allow them to transfer so I'm literally not backing up 100% of my files.

Is there a solution to this? Can I set windows 7 to allow any length file names?

The best way that you have to do, is to use the Long Path Tool. This is the answer to your problem. You should try it.

---

Sorry. Thread locked because you are four and a half years late to the party.

Harvey
Senior AnandTech Moderator/Administrator