Skip to content

AzCopy Cannot Handle Long File Paths on Windows enabled long file name #3210

@TomLingWu

Description

@TomLingWu

Which version of the AzCopy was used?

Note: 10.30.0

Which platform are you using? (ex: Windows, Mac, Linux)

Windows Server 2019 Datacenter
Version 10.0.17763 Build 17763
The Windows long file name is enabled:

Image

Using a PowerShell script to test a long file name in that VM, and it works.

What command did you run?

azcopy.exe sync "https://xyz-test-account.blob.core.windows.net/test_container/test_very_long_file_data_90_00000000000000000000000000000000000000000000000000000000000000000000000000000000000_data_inputname_100_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000.csv.zip" "d:\longfilename_test\test_very_long_file_data_90_00000000000000000000000000000000000000000000000000000000000000000000000000000000000_data_inputname_100_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000.csv.zip" --from-to BlobLocal --compare-hash MD5 --check-md5 FailIfDifferent --log-level Debug --skip-version-check

What problem was encountered?

Final Job Status: Failed

The log error:

ERR: [P#0-T#0] DOWNLOADFAILED: https://xyz-test-account.blob.core.windows.net/test_container/test_very_long_file_data_90_00000000000000000000000000000000000000000000000000000000000000000000000000000000000_data_inputname_100_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000.csv.zip : 000 : File Creation Error destination file has no known flags that could cause issue (current set: 0) and azcopy was unable to clear the flag(s), so access will be denied: The filename, directory name, or volume label syntax is incorrect.
   Dst: \\?\D:\longfilename_test\test_very_long_file_data_90_00000000000000000000000000000000000000000000000000000000000000000000000000000000000_data_inputname_100_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000.csv.zip

How can we reproduce the problem in the simplest way?

Download a blob file, save it to a local path whose full path is at least 270ish characters long. Try to download it with AzCopy.

The same download AzCopy command will be completed if only the destination full path is not too long.

Have you found a mitigation/solution?

No, since we need to support long file names.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions