Filename too long issue...

[fffblackmage]

I was moving some files over to my new Samsung F4 2TB formatted as NTFS with GPT instead of the usual MBR. A few files could not be copied over due to an error stating the filenames were too long. I thought it is the file system that limits the length of the filename, not GPT or MBR. What's going on here?

 

[taltamir]

I don't know about GPT or MBR affecting it... but i know that file system is not the only issue...
there is file system, OS, the file copy program used (the OS's built in one, or a custom one used in certain tools, like backup programs, then there are sometimes different systems for different actions, such as copying over a network)...
so anyways, its not just a matter of FS.

You know, I am curious to know if NTFS compression could affect it as well, I never heard of it making a difference, but knowing how it works I theorize that it would... Anyone knows?

PS. just an FYI, the "filename too long" error means that filename + directory names are too long... the full filename is something such as:
C:\Games\Data\Saves\Blah blah blah.sav

So if you copy a file from "C:\Games" to "C:\Mybackups\Taltamirs backups\games" you might have this error purely because the directory and subdirectories total length is longer. This was an issue for me which is why I always backup to a shorter named folder than the original folder.

PS. seriously, why is there no "do not parse emoticons" checkbox anymore? there used to be one and it essential!

 

[Voo]

there is file system, OS, the file copy program used (the OS's built in one, or a custom one used in certain tools, like backup programs, then there are sometimes different systems for different actions, such as copying over a network)...
so anyways, its not just a matter of FS.

Yep, it just depends if the used API was updated to work with NTFS constraints or still just checks if path is greather than MAX_PATH. Which means using a program that uses an API that was written in the last decade should do the trick..

 

[fffblackmage]

I don't know about GPT or MBR affecting it... but i know that file system is not the only issue...
there is file system, OS, the file copy program used (the OS's built in one, or a custom one used in certain tools, like backup programs, then there are sometimes different systems for different actions, such as copying over a network)...
so anyways, its not just a matter of FS.

PS. just an FYI, the "filename too long" error means that filename + directory names are too long... the full filename is something such as:
C:\Games\Data\Saves\Blah blah blah.sav

Actually, the two locations are identical except for the drive letter. Sorry I didn't make this clear in my original post.

So... C:\Games\Data\Saves\Blah blah blah.sav is being copied to D:\Games\Data\Saves\Blah blah blah.sav, but I'm still getting that filename is too long error.


ROFL.... This is just stupid. I plopped the file I'm having trouble moving into a zip, renamed it, moved the zip to the new location, and unpacked it. No filename is too long error message. WTF?

So basically, Windows just doesn't like moving/copying files with long filenames?

 

[taltamir]

yap, your FS is fine with the file name, the windows explorer file copy algorithm is the one with the problem...
mmm, what OS are you using? windows XP? wind 7?

 

[fffblackmage]

I'm using Windows 7 Pro x64.

And I just realized I didn't need the zipping part.... Could probably have just renamed it and changed it back afterwards.

 

[Voo]

mmm, what OS are you using? windows XP? wind 7?

Doesn't matter, every explorer version I know of enforces the MAX_PATH limit, at least partially

 

[Emulex]

teracopy dude. avoid the cmd line it brings with it legacy restriction.

7zip works too esp 64bit

 

[taltamir]

Doesn't matter, every explorer version I know of enforces the MAX_PATH limit, at least partially

heh, I thought it got better with later versions, I guess I was wrong.

 

[Voo]

heh, I thought it got better with later versions, I guess I was wrong.

Yep, I don't see many reasons to keep it that way either, though shell extensions could be concerned.. error

 

[Old Hippie]

heh, I thought it got better with later versions, I guess I was wrong.

I'm pretty sure it did get better but I still hit the limit once in awhile too.

 

[RebateMonger]

A client has an SBS 2003 server with tens of thousands of files with ultra-long path names. Windows Explorer refuses to copy them. When I need to copy or move the files, I use MS' Robocopy command-line.

 

[Nothinman]

A client has an SBS 2003 server with tens of thousands of files with ultra-long path names. Windows Explorer refuses to copy them. When I need to copy or move the files, I use MS' Robocopy command-line.

Yep, Explorer's artificial restrictions are a pretty big fail.

 

[Old Hippie]

When I need to copy or move the files, I use MS' Robocopy command-line.

Command-line.....Uh Oh.....count me ignorant and out.

 

[fffblackmage]

teracopy dude. avoid the cmd line it brings with it legacy restriction.

7zip works too esp 64bit

Thanks for suggesting Teracopy! I'm already loving it!

 

[Emulex]

yeah and use the verify option - i've copied 1TB of 7z/rar files over to have them fail. not sure why - so i use the teracopy verify option now - it's slower but i've not seen an issue since. if an issue did come up i would know. knowing is half the battle

 

[fffblackmage]

That's exactly why I love it. I already moved about 500GB of crap from my aging 500GB internal HDD before you mentioned Teracopy, but now I'm using the verify feature to make sure everything copied over ok. I've have many instances of files failing CRC checks after moving things to my external HDDs, so this is a really nice feature.

Only one more problem remains for me... I'm getting weird random pauses during the verify. This also happened before I installed Teracopy and when I was moving data from my 500GB HDD to my new 2TB HDD. Normally, I don't move over so many files and so much data in one sitting, so this hasn't happened before. But since I am moving so much stuff, this "stuttering" is making this verify process much longer than it needs to be.... not sure if this also happens for copying things using Teracopy, since I haven't tried yet.

 

[Mark R]

There is a long path API in windows, but because of the compatabiliy probs that can arise, it is little used (and poorly supported - e.g. Even .NET 4 has no long path support)

That doesn't stop some software trying to mitigate things. E.g. Windows explorer tends to use the old DOS style short names (e.g. PROGRA~1) for directories internally, but only shows the normal file name/ directory name. This doesn't always work (e.g. When creating a new directory, you have to give the full name) so you get the bizarre phenomenon that files can be accessed without difficulty but can't be copied.

 

[Elixer]

I will suggest you to use long path tool.It can help you with this problem.

I suggest you look at the date of the post. You don't think they fixed in in ~7 years?

Too bad these old posts can't get locked.

 

[hal2kilo]

I suggest you look at the date of the post. You don't think they fixed in in ~7 years?

Too bad these old posts can't get locked.

Necro threads are awsome.

 

[taltamir]

Necro threads are awsome.

even better if you actually wear a necromancer costume while doing it

 

[Puffnstuff]

Meh old or not this problem still persists today in windows 10 and I see it on a regular basis. I've had to pare down directory and subdirectory names along with shortening file names to transfer them.

 

[Shmee]

Parted Magic? Linux boot?

 

[jkauff]

My favorite file manager, Total Commander, gives you a warning about long file names--simply that some programs might not be able to access the file--and then allows you to continue, skip, or rename the file. As usual for TC, the best approach to the problem.

 

[w3rd]

Remember directory opus ftw...