Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to delete the files not completed automaticly when fileshare is full. #2685

Closed
v-youxie opened this issue May 17, 2024 · 7 comments
Closed

Comments

@v-youxie
Copy link

Which version of the AzCopy was used?

10.24.0

Note: The version is visible when running AzCopy without any argument

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 "C:\Users\v-youxie\Downloads\123" "https://xie********.file.core.chinacloudapi.cn/testing?sv**********************************************" --preserve-smb-permissions=true --preserve-smb-info=true --recursive

What problem was encountered?

I have an Azure fileshare with 1GB quota. While the whole size of the source directory is 1.2GB(11 files)
When uploading source directory to Azure fileshare. The process ended witwithin 10s(obviously no file transferred completly). The file transfers completed is 0. But in Azure fileshare ,some files generated. They consume capacity,but ccould not be used cause not completed.

image
image

In more tests, the file transfers completed changes randomly. Still a lot of uncompleted files generated in Azure fileshare.
image
image

First of all , uncompleted files need to be deleted automaticly to keep the consistency.
Secondly, when the source size is larger than fileshare quota, need to have a certain policy,no matter fullfilling the fileshare or uploading nothing,rather than uploading some of the files randomly.

How can we reproduce the problem in the simplest way?

Create a Azuzre fileshare,change the quota to a small number.
Upload a directory larger than fileshare with azcopy.

Have you found a mitigation/solution?

no

@adreed-msft
Copy link
Member

Normally, we would delete failed objects. In this case though, it seems AzCopy got back a 403... Typically, we interpret that as the literal meaning of the status code (forbidden, access denied), and exit the transfer early. In this case, this isn't the correct behavior. This is a bug. Thanks for reporting this!

@adreed-msft
Copy link
Member

I've put this into our backlog for next release, but, no guarantees that will be in the next release.

@wonwuakpa-msft
Copy link
Collaborator

Hi! @v-youxie Thanks for reporting this. Could you clarify what you mean by "uncomplete" files. Do you mean the upload not transferring all the files? Also, you can increase your standard file share quota and cost will be based on your actual usage.

@v-youxie
Copy link
Author

v-youxie commented Nov 15, 2024 via email

@wonwuakpa-msft
Copy link
Collaborator

A fix for this bug is in our backlog for next release. If you still have access to it, please send over your log files and name(s) of the incomplete files. @v-youxie

@wonwuakpa-msft
Copy link
Collaborator

Hi! checking in on this @v-youxie we would like to fully repro and diagnose the bug you encountered.

@gapra-msft
Copy link
Member

Closing based on lack of response.

Please increase file share quota and resume your job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants