Problem with rsync --inplace very slow/hung on large files

I'm trying to rsync a very large (62gig) file from one machine to another as part of a nightly backup. If the file does not exist at the destination, it takes about 2.5 hours to copy in my environment. But, if the file does exist and --inplace is specified, and the file contents differ, rsync ei

Re: [rsync-announce] Rsync 2.6.4pre3 released (Out of Office)

I am out of the office Wednesday March 16th through Friday March 18th. Will return on Monday, March 21st. Thanks. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Rsync 2.6.4pre3 released

I've released rsync 2.6.4pre3. I'm hoping that this will be pretty close to the final version for 2.6.4, so please beat on this and let me know if anything weird turns up! IMPORTANT: protocol 29 was revised in pre3 to be incompatible with pre1 and pre2, so be sure to update all your pre-release v

[Bug 2455] rsync --daemon segfaults if "log file = " dir does not exist

https://bugzilla.samba.org/show_bug.cgi?id=2455 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: include/exclude client/server precedence

ok, wayne: thank you a lot, next question in another thread now im using: include = [oO][uU][tT][lL][oO][oO][kK].[pP][sS][tT] [aA][lL][mM][aA][cC][eE][nN].[pP][sS][tT] exclude = *.[pP][iI][fF] *.[iI][sS][oO] *.[mM][oO][vV] *.[mM][pP][33] *.[wW][aA][vV] *.[eE][xX][eE] *.[dD][lL][lL] *.[pP][

[Bug 2455] New: rsync --daemon segfaults if "log file = " dir does not exist

https://bugzilla.samba.org/show_bug.cgi?id=2455 Summary: rsync --daemon segfaults if "log file = " dir does not exist Product: rsync Version: 2.6.3 Platform: Sparc OS/Version: Solaris Status: NEW Severity:

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

On Tue, Mar 15, 2005 at 12:39:54PM -0600, [EMAIL PROTECTED] wrote: > Dunno if this has any relationship (or even if this is the right place to > break in) Seems like a decent place to jump in to me... Welcome! > SERVER: rsync-HEAD-20050314-2227GMT > rsync error: protocol incompatibility (code 2)

RE: rsync error: protocol incompatibility (code 2) at main.c(451)

green newbie. (You guys are too fast) CLONE: rsync-HEAD-20050315-1733GMT] [EMAIL PROTECTED] local]# rsync -avPLz --password-file=/etc/rsync/rsync.2bb [EMAIL PROTECTED]::mysql-2bb/srv/b* /tmp/ receiving file list ... 6 files to consider bm.MYD Invalid file index: 65536 (count=6) [sender] rsync er

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

;ve checked in a fix to CVS, > and the latest "nightly" tar file has this fix present. I'm confident > that will take care of the problem for you. Thanks for the help! Great service. :) I will package rsync-HEAD-20050315-1733GMT and send some feedback. Thanks

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: > Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS, and the latest "nightly" tar file has this fix p

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

On Tue, Mar 15, 2005 at 06:54:16AM +0100, Dag Wieers wrote: > Another update. Only some of the hardlinks seem to be actually missing. > Does this make any sense ? Yes, that gives me something to go on for testing. I should hopefully be able to reproduce what is going on. ..wayne.. -- To unsubsc