azure-storage-azcopy: On Windows, AzCopy Cannot Handle Long File Paths
Which version of the AzCopy was used?
10.0.3-preview
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
.\azcopy.exe copy "..\..\1234567891234567981234567981321321654684354645313216843513213223111141445 45474567271271727231731324175417234173241732417324173aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbb" "https://REDACTED.blob.core.windows.net/uploadtohere?REDACTED"
What problem was encountered?
On upload, AzCopy failed with the error: failed to perform copy command due to error: cannot start job due to error: cannot find source to upload. For download, it seems like AzCopy can handle slightly longer paths, but there is still a point where it fails.
How can we reproduce the problem in the simplest way?
Create a file, whose full path is at least 250ish characters long. Try to transfer it with AzCopy.
Have you found a mitigation/solution?
No.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 23 (13 by maintainers)
Hiya, we currently have a refactor in progress and will be fixing this up shortly after we finish refactoring upload and download.
I’ll have to walk back on that. I realized that the previous times, I did not have verbose logging. So, I ran again with verbose logging on and it is now working and transferring at a decent pace compared to ASE. Strange thing is, otherwise, the command was identical - it was a batch file and I just appended the logging. Not sure what the issue was the first time but I can’t imagine turning on logging would fix it.