DO NOT REPLY [Bug 5695] improve keep-alive code to handle long-running directory scans
https://bugzilla.samba.org/show_bug.cgi?id=5695 tim.l...@alcatel-lucent.com changed: What|Removed |Added CC||tim.l...@alcatel-lucent.com --- Comment #5 from tim.l...@alcatel-lucent.com 2010-10-27 00:29 CST --- These bugs seem to be related (having similar error messages: connection unexpectedly closed, broken pipe, timeout). bug7757 with big file, rsync times out out when it should not; the sender is still responsive bug2783 Random high loads during syncs (server side) / client stream errors rsync: connection unexpectedly closed (2761332 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(365) bug5478 rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32) rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32) io timeout after 30 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.2] bug5695 improve keep-alive code to handle long-running directory scans ./io.c:void maybe_send_keepalive(void) bug6175 write last transfer status when timeout or other error happens rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed (99113 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.5] bug7195 timeout reached while sending checksums for very large files -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5695] improve keep-alive code to handle long-running directory scans
https://bugzilla.samba.org/show_bug.cgi?id=5695 --- Comment #4 from wwen...@sbcglobal.net 2009-04-09 17:49 CST --- I echo the thanks for all your hardword making rsync available to the masses. I'd just like to add to this defect that I have a system where disk writes can be very slow when my client is very loaded. In my system, rsync gets lowest priority to use disks on the client. Some very large files in my directories can take a long, long time to create (longer than the 10 minute timeout I need to use on client). I am not using --copy-files but I am getting a local copy because my very large files are often mostly unchanged (just a byte in a gigantic file) or only a timestamp change. So the receiver is creating the temp file from an existing file which is usually 100% or 99.99% the same. I am stuck in the file creation loop in receiver.c/fileio.c for more than 10 minutes because write() is slow but it does make slow progress. Just for fun, I simulated my problem on a fast Linux client by hacking in a msleep(20*1000) in the flush_write_file() loop on the client rsync so that each local file copy update takes much longer than the client timeout. The server times out on the client in this test scenario too. I would love it if someday you could make a keep alive, or equivalent, for file creation and not just for directory listing. I'll do a workaround by making a huge timeout on the server /etc/rsyncd.conf so that it does not timeout on the client. By the way, here is my rsync command line; nothing fancy here except the timeout. Yes, I'm using a slow FAT drive (I have no choice here): rsync --modify-window=3602 -ptO -L --delete-during -v -ii --progress --port= 873 -z -r --bwlimit=0 --timeout=600 myserver::rtdata/mydir destdir -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5695] improve keep-alive code to handle long-running directory scans
https://bugzilla.samba.org/show_bug.cgi?id=5695 [EMAIL PROTECTED] changed: What|Removed |Added Summary|rsync local timeout |improve keep-alive code to ||handle long-running ||directory scans Version|3.0.3 |3.1.0 --- Comment #3 from [EMAIL PROTECTED] 2008-09-06 09:49 CST --- please note that directory dati/Documenti/Gabriele/Maildir/.Bugtraq.2006/cur/ contains some thousands of files. A simple ls command on this folder, takes many minutes to complete. Unfortunately, this is not something that rsync currently has keep-alive code inside (the directory scanning code). The timeout value currently needs to be set high enough to handle the largest directory scan, and (if something like --copy-file were used) the largest local-file copy the generator might do. The only thing you can currently do is to increase the timeout to the point where it doesn't fire during a successful transfer. This would be something that would be good to improve for 3.1.0. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
