Forum Discussion
AzCopy files with no data
Has anyone had an issue with AzCopy where it appears to copy files to Azure Storage File Shares, where the file is created but contains no content.
We are using AzCopy to migrate large numbers of documents from a file server (NTFS) to File shares in Azure Storage. We noticed that about 10% of the files being copied appear to copy correctly (no errors logged) but are missing the file content.
We end up with a blank file but the file size is the same as the source.
After we discovered the issue, we copied the files again to a different location in the same Azure Storage and the files copied correctly.
Any help or suggestions would be appreciated!
Thank you
Steve
take this and check the log:
Find errors & resume jobs with logs in AzCopy (Azure Storage) | Microsoft Learn
7 Replies
- Paul_Newton_-_MarcoCopper Contributor
Hi Steve,
Did you resolve this problem? - We have an Azure partner who is having the same issue, (TBC) when transferring .xml files to our data exchange system. Some files arrive fine and intact, but occasionally they seem to arrive empty, opening in Notepad++ shows NUL chars.
Thank you,
Paul.
- Hi Paul, we haven't found the root cause of this issue. We submitted logs via a support call but haven't resolved the problem. Microsoft support have asked us to contact them if we have anyone instance of the issue. I am wondering if it relates to caching on the source file system.
- Paul_Newton_-_MarcoCopper Contributor
SteveKnutson Thank you for the reply Steve. I will update this thread if we find the cause and any resolution.
take this and check the log:
Find errors & resume jobs with logs in AzCopy (Azure Storage) | Microsoft Learn
- samy_vanderspikkenBrass Contributor
We need to check the logs in order to know exactly what is going wrong.
AzCopy creates log and plan files for every job.
By default, the log and plan files are located in the %USERPROFILE%\.azcopy directory on Windows or $HOME$\.azcopy directory on Mac and Linux.
To review the logs go to the default file location and open the .log files:
If you need more help reviewing the logs, please feel free to share them!
- Thank you, that's a great help. I'll track the logs down and have a look.