similar to: Fw: Rsync's Speed

During my initial download for my home directory backup, it took rsync over 6 hours to do the initial backup, but I can FTP the stuff in about 30 Mins. Is Rsync usualy this slow? I have compression turned on, and its across a 100 MB/S network, Anyone had this problem before? Steve Sills

Hi, Whenever i am using the command rsync --write-batch -av --stats `cat $1` -e ssh user@remote machine:/destination/ This is writing rsync_argvs files in the home directory as well as to the destination directory. Can anyone give me any idea as how to prevent the writing of rsync_argvs files in the home directory which is of no use. Regards, Surabhi. > ---------- > From:

-----Original Message----- From: Susan Ator Sent: Wednesday, March 26, 2003 12:32 PM To: 'jw schultz' Subject: RE: Logging on the rsync server from a client connect Thanks. It turns out I needed to add rsync to my ipchains. Once I did that I was able to connect correctly and log the information. I knew it was something really really basic on my end. sa -----Original Message-----

Actually, what I do also propogates deletions. Since someone may unpack a tar containing files with earlier mtimes than a marker file, a simple --newer won't do it for us, either. Instead, I generate a list of all items, consisting of name and type, to which i append number of links, size, and mtime for files; link destination for symlinks; and for directories, fifos, chars, blocks,

On Thu, May 15, 2003 at 10:40:21PM -0500, Lee Eakin wrote: > > Date: Thu, 15 May 2003 20:11:09 -0700 > > From: jw schultz <jw@pegasys.ws> > > Subject: [RFC] report options > > > > I have hinted in the past of wanting to go to a more > > selective control of the output of rsync. Here it is. > > > > Sounds very cool. I'm guessing that a

That's actually a very good suggestion. First I figured that in this way files changed within the hour after creation would be ignored, but they probably represent a very small minority anyway. On the other hand, this does not really rectify the situation, but will allow us to postpone the real sync again until, let's say a holiday, where we have plenty of time to sync. Rgds, Bart

On Tue, Sep 16, 2003 at 03:49:45AM -0700, jw schultz wrote: > > Aside from numerous other weaknesses that have crept into > the manpage i do note that there doesn't seem to be any > point where it is mentioned that rsync replaces destination > files rather than updating them in-place. I'm not sure > where it would go in the current manpage. > > I'm no writer

rsync commandline: /usr/bin/rsync -e /usr/bin/ssh --archive --compress --sparse --verbose --stats --delete --numeric-ids --partial --relative --one-file-system target.host:/ /destination/path/ target rsync version: 2.6.3 destination rsync version: 2.6.2 The server we're trying to synchronize contains directories within "/" that are mounted to other locations within

Just built 2.6.1 and started testing it. Nice job guys. I especially love the --progress and hardlink tweaks. Quite often, while I have systems backing up out of cron, I'd love to be able to see the --progress. Unfortunately, it's just not practical to crank up the verbosity like that on a regular basis (some of these systems have a few million files). A neat feature I'd like to see

What I want to do is use rsync to back up a folder to an external drive. I would like to keep 30 days worth. For example: I have backups of June 1 - June 30. Once July 1 comes along, I want to keep June 2 - July 1 and delete June 1, and so forth. Any ideas how I can accomplish this? -- View this message in context: http://www.nabble.com/Rysnc-Schedule-tf4104577.html#a11672997 Sent from the

On Thu, Aug 28, 2003 at 12:51:16PM +0300, Sviatoslav Sviridov/Lintec Project wrote: > > Sorry for direct reply, but mail server at samba.org blocks my messages. Postmasters, Martin, For your consideration. > Begin forwarded message: > > Date: Thu, 28 Aug 2003 12:43:54 +0300 > From: Sviatoslav Sviridov/Lintec Project <svd@lintec.minsk.by> > To: rsync@lists.samba.org

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are

> > Message: 10 > Date: Tue, 20 May 2003 17:02:35 -0700 > From: jw schultz <jw@pegasys.ws> > Subject: Re: Problem with (corrupt?) file (fwd) > To: rsync@lists.samba.org > Message-ID: <20030521000235.GB29561@pegasys.ws> > Content-Type: text/plain; charset=us-ascii > > Is it the same files each time? > What versions of rsync? > Is this over NFS? >

Just got this from our nightly backup rsync: overflow: flags=0x6e l1=99 l2=1952984691 lastname=var/www/manual/mod/mod_php4/de/function.get-exte ERROR: buffer overflow in receive_file_entry rsync error: error allocating core memory buffers (code 22) at util.c(238) Command exited with non-zero status 22 real 5.15 user 1.00 sys 0.88 Rsync version information: [root@gluon root]# rsync

I've been getting this error message for a few days from a customer's server and we can't seem to decipher it. I googled for it and only found references to it with respect to much older versions of rsync. We're running the Debian packaged version of rsync version 2.6.2-3. The customer side is running 2.6.3 compiled from source. #### inflate (token) returned -5 rsync error:

Have the hard-links optimizations that were described here been implemented? http://lists.samba.org/archive/rsync/2004-January/008137.html In any case, what's the general consensus behind using the --hard-links option on large (100GB and above) images? Does it still use a ton of memory? Or has that situation been alleviated? ..Chuck.. -- http://www.quantumlinux.com Quantum Linux

On Fri, Jan 17, 2003 at 05:42:41PM -0800, Wayne Davison wrote: > On Fri, Jan 17, 2003 at 04:21:59PM -0800, jw schultz wrote: > > It should not do /root2/i386/etc/init.d/rsyncd and so on as > > -R would have it. > > -R would only do that if you actually prefixed the paths with the source > dir, which is not what happens with --files-from. The source dir is > just used

Hi all, I'm new to the rsync list. I've been searching for two days and have tried five different installs and so far none work the way I need them to. I have an "backup" server running rsync --version: rsync version 2.6.6 protocol version 29 Copyright (C) 1996-2005 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard

Here is an update to the project ideas list for GSoC/EVoC. If there are no complains within the next few days, I just go ahead and add them to the wiki page. Many thanks for reviewing and suggesting changes! Instruction Scheduler Difficulty: Difficult Skills Required: C++ Useful skills: Compilers Hardware/Software required: NVIDIA Fermi or later Where to ask questions: nouveau at

Any feedback on this patch and the possibility of getting it into CVS or the patches directory? Thanks, Craig ---------- Forwarded message ---------- To: jw schultz <jw@pegasys.ws> From: Craig Barratt <cbarratt@users.sourceforge.net> cc: rsync@lists.samba.org Date: Sat, 01 May 2004 17:06:10 -0700 Subject: Re: setting checksum_seed jw schultz writes: > > > There was some