similar to: [Bug 10451] New: --info=progress2 with --bwlimit doesn't give correct value

https://bugzilla.samba.org/show_bug.cgi?id=10450 Summary: --info=progress2 increase % Product: rsync Version: 3.1.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: vania.toperich at gmail.com

https://bugzilla.samba.org/show_bug.cgi?id=10580 Summary: Total file size reported wrong with --stats --info=progress2 Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=9660 Summary: rsync --daemon --bwlimit does not work on server side Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mopp at gmx.net

Hi, I'm a bit new to rsync, and I recently learnt about the --info=progress2 flag to display complete transfer progress. However while transferring I encountered some unusually large transfer rates being displayed repeatedly. I used "rsync -av --info=progress2" to transfer a folder with several large files. Every time a new file was started , the initial transfer rate was unusually

I am using rsync version 3.0.7. My rsync server is running on the cloud. I have set the bwlimit to 10 i.e. 10 KBps. When I try to sync files the bwlimit is as what is set. I have enabled storage of partial files. When a communication break causes rsync to time out during a transfer the partial file is stored in the partial directory. I then try rsync again when the link is up. At this point I see

Hi there: I am testing rsync with a large number of small files. I am using 'tee' to keep the log, and I noticed that the log file was growing very quickly. It seems that the progress text refreshes too often: building file list ... ?0 files... ?100 files... ?200 files... ?300 files... ?... ?5.53G? 95%??? 8.50MB/s??? 0:10:20 (xfr#478709, to-chk=9/537759) ?5.53G? 95%??? 8.50MB/s???

https://bugzilla.samba.org/show_bug.cgi?id=7120 Summary: Variable bandwidth limit .. bwlimit Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: pmdumuid at gmail.com

https://bugzilla.samba.org/show_bug.cgi?id=8375 Summary: rsync with bandwidth limit sometimes expend extra time Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: fbmoser at

https://bugzilla.samba.org/show_bug.cgi?id=6881 Summary: --bwlimit option uses KiB/s, but is documented as (what amounts to) kB/s Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned at

# Environment (both local and remote hosts): $ /usr/bin/rsync --version rsync version 2.5.7 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums $ uname -a Linux dbrac-01 2.4.9-e.27enterprise #1 SMP Tue

I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2 servers "wilber" (the remote archive) and "judy" (the local archive) connected with a gig

Hi, I Emailed this afternoon that bwlimit leads to a much too low bwlimit if small amounts of data are sent in each write. I wrote a small patch now. Congrats on the code: It's nice and clean: I wrote a working patch in 5 minutes after examining a total of 25 lines of code. (My backup used to require two hours of small sleeps alone, which should be reduced by a factor of 8....)

https://bugzilla.samba.org/show_bug.cgi?id=2800 Summary: bwlimit effects checksum speed Product: rsync Version: 2.6.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: schwern@pobox.com QAContact:

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

Hi list, I couldn't find anything related to this, on mailing lists or even bugzilla, so here it is. A problem with this combination exists in the new 2.6.3 where the bwlimit code got rewritten and is not present at <= 2.6.2. The problem is that on io.c:882 bwlimit_writemax is also used to control the bandwidth, but it is not initialized for the daemon mode. At options.c:772 you can see

[I'm not subscribed, please CC me on replies] Some time after 2.6.0 the --bwlimit code was enhanced, but the code now doesn't work anymore when you set the bandwidth limit for the daemon and generates error log entries like: 2005/01/13 08:17:03 [29636] rsync: writefd_unbuffered failed to write 12 \ bytes: phase "unknown" [receiver]: Success (0) 2005/01/13 08:17:03 [29636]

Does "bwlimit" option really work on rsync locally? We have one type of harddisk and want to slow down rsync I/O on disk because I don't want the disk head gets too hot. While I'm trying to use --bwlimit option, it looks the rsync speed was slowed down, but iostat is not improved at all. In both case the block written speed is increased by the same amount. How could I really

Wayne replied to my original note which said that in a special situation that I was using to probe rsync to build a behavioral model that bwlimit= resulted in bimodal behavior around a 4000 kbyte/sec value. He responded with a patch that I have tested in a limited way. I have a push scenario from a local site to a remote site. I use a file that is 6.3 Megabyte in size whose checksums (when

Hi, I have two issues with the --bwlimit parameter to rsync which are not mentioned in the FAQ (please correct me if I am wrong): 1. When both an rsync client and an rsync daemon specify the --bwlimit parameter, the client's value overrides the server's value. This could be used in a DOS attack if the client uses a larger value than the server intended. The documentation also is

Hello! I cant get the bwlimit option working right. If i set this option over 400 kbyte per sec i still only get 400kbyte per sec, whether wich value i set. I try this option with a 100MB big file. I use a debian stable System with rsync version 2.5.6cvs protocol version 26. Can someone tell me how i can this get working? thx Rene dpkg -l "rsync*" ii rsync 2.5.5-0.1 fast remote