Rsync hangs incremental file list

I said - nothing unusual, because they are identical to what I see in other unrelated to this problem PC. Remember I said in the first posts Remember, it need many tries to get to the "stuck state" -- some days or weeks. Because rsync on individual file unstacks Wishmesh - I could not figure it out why that happen but However, Cygwin or Msys2 use modified windows program and considered to be able to be run within Windows filesystem ; They don't have the same concept of DrvFS and VolFS but they use another approach.

I thought, if you could fix the point of condition when that problem occurs, i. I don't understand therealkenc 's saying enogh but I couldn't resist to try Good question; You know, people say good question when they don't know a quite answer. I cannot be sure that's filesystem issue; I'm just guessing it might be or not and it could be timestamp related issue if it might be a filesystem issue.

Of course, it might not be timestamp related, it might even not filesystem issue, it might be a issue I could not imagine. Sorry my poor explanation. Something is getting borked on the server side. We don't know what, because no server side strace. But I think you'll have a lower probability of borkage on the server if you push to VolFS, because smart money says this is a DrvFS "filesystem thing". There's no problem we can see on the client. Once you push to any different folder without corruption you're golden.

Go deeper, sideways, to a whole different server, whatever. Hold on to the corrupt folder in its pristine corrupt state if you have the space. The devs are going to need diagnostics of some kind on that tree, because no one will be able to repro this locally. You've got a real bug. But note that the chances of anyone reading this far down the thread is rapidly decreasing.

Adding SvenGroot to see if he can help out with this one. Also, marking this one as a bug. That may provide some insight in to what is happening. There's gotta be a way to collect a server-side strace but it isn't immediately obvious to me.

The client-side he supplied above. It hangs on:. The problem isn't network-related because the problem persists across a reboot and only once the DrvFS filesystem on the server-side has gotten into a corrupt state. Since the server is also WSL, logs of both sides would be helpful. Strace would be helpful but I can see why that would be difficult in this scenario.

However, ETL logs should be easy if you have access to the server. I'm experiencing this issue as well. It occurs on this image. I'm pretty sure this was fixed as -- I haven't seen it since upgrading to I am on and last month the rsync works great.

But today i can only use it when i use. I can confirm I've the same problem. So running below in a seprate console window resumes the file transfer. Thank you for this! I was able to use this as a workaround to copy a massive amount of data. Adding a -W to the rsync command line had fixed this problem for my rsync based backups for quite some time. But it recently got stuck again. I updated from Windows from to , updated WSL from So this definitely has not been fixed.

Running a "while killall -CHLD ssh; do sleep 0. It is really disappointing that after more than two years Microsoft has shown no interest in fixing really major bugs affecting basic linux tools like rsync. Can somebody check whether the issue is still present in WSL 2? It should be available in Windows Insiders by now. That was a week ago or so before I reinstalled Windows to get a somewhat stable OS again.

After some random time, rsync hangs, and resizing the bash window makes it continue. Autohotkey script to resize the window with bash command prompt where rsync is running under WSL.

This is still an issue in Microsoft Windows 10 Enterprise I am using rsync in the VS Code window, and it gets stuck. Resizing the window seems to unstick it for a little while. This just started happening for me today. I'm not sure why now, maybe a delayed Windows Update from my domain admins? This is totally unacceptable. It's amazing that nothing has been done about this after this amount of time. This is a really annoying issue. Following command is used to sync the files from source to destination.

Just like a file user can sync a directory from local computer to remote computer server. This command will use to sync the local computer to remote server.

The directory will be synched with files in that directory. Example 4: Sync Remote directory to local server. There are lot of requirements where user need to sync the remote directory to local directory. The rsync command is used to copy or sync the remote directory from remote server to local server. If the directory named test is not available on local server then rsync command internally creates directory as given in example. Using rsync user can use the ssh to secure data transfer from one server to other server.

User can transfer the data from with secured connection. With using ssh nobody can read the data while it is being transferred over the wire. I will give the example to copy file from remote server to local server using ssh and vice-versa. User needs to use —e option to perform data transfer. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. You should upgrade to rsync 3. Even so, it will probably take a long time to go through all that data.

In my case it still takes over an hour between two pretty powerful DL G5 servers. You noted earlier that du was hanging as well. Something is up with this filesystem, and rsync is hitting whatever du was.

One quick thing you can check is for kernel error messages indicating a disk problem. Type dmesg and see what's at the bottom. The hang after the message "building file list Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Learn more. Thank you. Last seen: 5 hours 56 min ago. Do you use the same options. Thank You for your. Thank You for your reply. Yes, I have the same version in Client and Server. Last cwRsync version 2.