-
Notifications
You must be signed in to change notification settings - Fork 822
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
rsync not copying #97
Comments
I see you're rsyncing over ssh... could it be something screwy with ssh rather than rsync? Try adding It's also possible that it gets confused because /mnt/e/ is presumably a native Windows FS of some sort. Might want to strace and see where it gets stuck. |
Here is the strace (
|
Not But the other symptoms do sound like it's just choking on large files. Hopefully someone at Microsoft has further ideas. |
Ahh, sorry about that. Still didn't help though. Here is the result of
And with strace, here is the result of
|
Problem persists with Build 14328 |
No comment since April. Closing for now. If problems persist on builds after than 14936, please let us know, |
I'm running in this exact same issue on Windows 10 Pro (Version 10.0.14393 Build 14393). After just a few transferred files rsync just hangs. I also suspect it's something related to SSH on the client (Windows) because when I run a tcpdump I can see that the last packet is a TCP ACK from the client. I ran the rsync command with the -e "ssh -vv" parameter and once the transfer is stuck the last few lines are just:
It used to work fine a few weeks ago, so I suspect that something broke during a recent Windows Update. When I stop the process by sending CTRL+C the terminal returns this:
And after 60 seconds:
Hope this helps. |
@acastaner -- is it possible that you are in fact hitting #610 or #616 ? I've seen that issue start happening mysteriously / with no apparent cause; it's a race condition so the actual cause is typically some subtle environmental change that has some slight effect in how long one code-path takes to execute as compared to another. If so -- those two issues (and a whole bunch more that could be releated) are fixed in recent Insider builds. |
Right, I'll switch to an Insider Build and see what happens. |
Switching to an Insider Build (using the Slow branch, not sure which one to use) didn't fix the issue unfortunately. |
Hm... Do you know exactly which build you got? (Run |
I'm running Microsoft Windows [Version 10.0.14986]. |
Hm... I could be misremembering, but I thought the issue I was wondering about was fixed in build 15002. (The latest Insider Fast Ring build is 15048; I don't know what the latest Slow Ring build is offhand.) Is there any chance you could try a newer build? |
Well I've switched to the Fast Ring a few days ago but I'm apparently not getting any new version (still stuck at build 14986). I'll look around to see if I can somehow trigger/force an upgrade so 15002+. |
Now running build 15048. Issue with rsync remains the same :/ |
I'm on 15063 and running into the same issue, transfers a few files and then just stalls,
|
same problem. dry run goes ok. |
also SCP of files runs ok. |
When I run rsync to a computer that is on my local network running Ubuntu server, it detects all the changes that needs to be made just fine and starts iterating through all the files and can do dry runs as well, but as soon as it hits a file that needs to be copied, it just gets stuck as 0% and never progresses.
Here is the command that I used:
rsync -r -vv -u -t --progress --delete-after --force --ignore-errors --chmod=755 /mnt/e/ adam@gangster:/media/tier_3
.Note that it runs just fine in cygwin and I've been running it for years, with just the local path adjusted of course.
I can SSH to the system, so that part works fine.
The text was updated successfully, but these errors were encountered: