-
Notifications
You must be signed in to change notification settings - Fork 812
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
wsl rsync - Getting loads of "write failed 11: Resource Temporarily Unavailable" #11237
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
/logs |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue. Thank you! |
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
Windows Version
Microsoft Windows [Version 10.0.22621.3155]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1
Distro Version
Ubuntu-22.04
Other Software
No response
Repro Steps
Whenever I run rsync in wsl to copy remote files to my wsl VM I get this strange issue.
A load of files don't get copied due to this error:
write failed 11: Resource temporarily unavailable
If I run the command multiple times it eventually all syncs and the error disappears, but it usually takes a few tries.
Running the command to rsync in the other direction there are no issues.
Expected Behavior
Actual Behavior
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: