Hello everyone, I'm getting strange module sizes in the logs. (2.6.9) This is the command: rsync -anr --delete --omit-dir-times --stats -e "ssh -i access.key -l pluto -p 22" --files-from=config\templist "/cygdrive/C/" sv_rs@192.168.10.49::Accounts After updating all the files on the "Accounts" module, the size is reported correctly on the receiver log file as: 2007/01/08 18:24:24 [30153] sent 22485 bytes received 27427 bytes total size 68937712 * This is the real size (around 68MB), however, having started with an empty dir on the receiver, the number of bytes received is not correct!? (I guess it should be similar to total size). Following this, I perform another run (this time no files updated), which shows the following log: 2007/01/08 18:27:00 [30220] rsync to Accounts from sv_rs@unknown (192.168.10.50) 2007/01/08 18:27:00 [30220] receiving file list 2007/01/08 18:27:00 [30220] sent 85 bytes received 27427 bytes total size 137875424 * Note that without changing anything, the total size has exactly doubled. The strange thing is for the both operations, the sender side reports correctly: for example for the first operation: sent 69019827 bytes received 22416 bytes 288276.59 bytes/sec total size is 68937712 speedup is 1.00 Any clues? Julian
Am Montag, 8. Januar 2007 18:51 schrieb Julian Pace Ross:> Hello everyone, > > I'm getting strange module sizes in the logs. (2.6.9) > > This is the command: > rsync -anr --delete --omit-dir-times --stats -e "ssh -i access.key -l > pluto -p 22" --files-from=config\templist "/cygdrive/C/" > sv_rs@192.168.10.49::Accounts >...> > Following this, I perform another run (this time no files updated), which > shows the following log: > 2007/01/08 18:27:00 [30220] rsync to Accounts from sv_rs@unknown > (192.168.10.50) > 2007/01/08 18:27:00 [30220] receiving file list > 2007/01/08 18:27:00 [30220] sent 85 bytes received 27427 bytes total size > 137875424 > * Note that without changing anything, the total size has exactly doubled. >Can you show the content of "config\templist"? Manfred
Dear List, I have noticed something regarding this: running the following command from a WinXP: rsync -av --progress --stats -e "ssh -l julian -i rsync_key" \ "/cygdrive/c/FILES/" 192.168.100.100::filesbak gives the following log output on the receiving side (rsync 2.6.9 / suse): 2007/01/09 10:12:14 [23770] sent 44 bytes received 88307 bytes total size 1334942737 which is good. Running the EXACT same command on the XP side, *but this time with the --delete option*, gives the following in the logs on the linux receiver side: 2007/01/09 10:13:46 [23780] sent 44 bytes received 88319 bytes total size 2669885474 Note change in total size. I can safely say from a couple of tests that this behaviour is the same when using the rsync daemon on port 873 rather than ssh. Also, I noticed that the receiver never reports the correct number of received bytes (it is always around 88000 as seen above, irrespective of the files it updates). The sending side (2.6.8 / XP) reports all sizes correctly. Can someone please replicate or am I missing something? Regards Julian> Can you show the content of "config\templist"? > > Manfred > --I guess its no longer relevant. This is the module on the linux side: [filesbak] path = /FILES read only = false uid = root gid = root incoming chmod = g-rwx,o-rwx list = false
I see.. if the change is only in the make_file routine, then I can compare the two versions of this routine, update and recompile right? Also does this have anything to do with the bytes sent/received being inaccurate? I am getting (again on the daemon) for example "bytes received 20000" when I would have just transferred several Megs. Again, thanks ----- Original Message ----- From: "Wayne Davison" <wayned@samba.org> To: "Julian Pace Ross" <linux@prisma.com.mt> Cc: <rsync@lists.samba.org> Sent: Tuesday, January 09, 2007 8:53 PM Subject: Re: strange file sizes in log> On Tue, Jan 09, 2007 at 08:14:51PM +0100, Julian Pace Ross wrote: >> Will there be a nightly update? > > Yes. Do note that CVS is a work in progress towards 3.0.0, and is under > heavy development at the moment. It also has a new protocol, 30, which > will not be the final protocol 30 until 3.0.0 is released, so you do > need to be careful to either not mix different 3.0.0-cvs versions (since > the protocol may have changed), or to make the transfer talk protocol 29 > (which can be done by using the --protocol=29 command-line option, or > for all transfers by changing the PROTOCOL_VERSION define in rsync.h). > > ..wayne.. >