similar to: rsync hangs in read_int (generator.c line 498)

Mark II of the patch set. The first patch (dynsumlen2.patch) increments the protocol version to support per-file dynamic block checksum sizes. It is a prerequisite for varsumlen2.patch. varsumlen2.patch implements per-file dynamic block and checksum sizes. The current block size calculation only applies to files between 7MB and 160MB setting the block size to 1/10,0000 of the file length for a

Currently rsync has a bit of a problem with very large files. Dynamic block sizes were introduced to try handle that automatically if the user didn't specify a block size. Unfortunately that isn't enough and the block size would need to grow faster than the file. Besides, overly large block sizes mean large amounts of data need to be copied even for small changes. The maths indicate

I'm in the midst of coding a patch set for consideration that will bump the protocol version and have a couple of observations. The current minimum backwards-compatible protocol is 15 but we have code that checks for protocol versions as old as 12. If someone else doesn't beat me to it i'm considering cleaning out the pre-15 compatibility code. A backwards compatibility patch could

Hello, I've been having all kinds of problems with rsync. I've tried versions 2.5.4-6. They all seem to have the same problems. Currently, I'm trying to use SystemImager, which uses rsync to transfer files. I get this: get_boel_binaries_tarball rsync -av 10.1.2.14::boot/i386/SMC/boel_binaries.tar.gz /tmp/ receiving file list ... ERROR: buffer overflow in recv_exclude_list rsync

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the IO.C module. The (char) type was being used where (void) was more appropriate based on the actual use of the code. The (char) type was also being used where the usage was actually an (unsigned char). const qualifiers were added to improve compile efficiency. EAGLE> type

Author of the message didn't include rsync@lists.samba.org in the reply, and I think this message is in topic. -------- Original Message -------- Subject: Re: rsync windows -> unix still hanging :( Date: Mon, 30 Dec 2002 17:24:47 -0800 From: Jim Kleckner <jek_subs@kleckner.net> To: Mike Rubel <mrubel@galcit.caltech.edu> CC: cygwin@cygwin.com References:

The attached patch adds some whitespace to the recv_files() function declaration, and renames variable 'f' to 'f_out' in generate_files(). -------------- next part -------------- Index: generator.c =================================================================== RCS file: /cvsroot/rsync/generator.c,v retrieving revision 1.93 diff -b -c -r1.93 generator.c *** generator.c 30 Jun

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

Wayne, Please consider the attached patch. This applies to the current CVS, and is independant of patches/local-batch.diff. As a matter of fact, I'm sure it would conflict heavily with local-batch.diff. This version of batch mode has a couple distinguishing features: Write-batch records (almost) the entire sender side of the conversation into one file. ("Almost" because it has

This draft patch adds support for transferring extended attributes with a new --xattr option. It ought to work on Linux with XFS or ext2/ext3 filesystems with the SGI/bestbits attribute system. It is partially working, but there seems to be some kind of hang bug while transferring the file list. I suspect it might be provoking a problem in io.c. You need to rerun autoconf, autoheader and

Hi All, Here's an rsync patch which adds an --offline flag, letting you transfer changed blocks via removable media, while still comparing checksums via the net. I expect this could be very popular for the growing number of people who want to do disk-based offsite backups, which is what I needed it for. It took me longer than I hoped, but still only several hours to work this out -- it

Dear rsync experts, I'd like to ask you a couple of questions. ***** 1. ***** If I'd like to send additional metadata for each block, what would be the easiest and less intrusive way to do this? The following seems to work: ---------------------------------------------------------------------------- diff -rupN ../rsync.git/token.c ./token.c --- ../rsync.git/token.c 2015-11-03

Wayne, It's taken a little while for me to get more familiar with the code, but I think I've reached a good breakpoint in improving batch-mode. Let me highlight some of the changes in the attached patch: * --write-batch and --read-batch arguments are no longer passed from client to server. This fixes the current problem that causes the server threads to die when the client

I have added regular expression support using a POSIX implementation. The patch (against 2.5.5) is attached. The implementation is simple and follows the same mechanism that is implemented for normal searches. I added these command line arguments: --rexclude=PATTERN exclude files matching regexp PATTERN --rexclude-from=FILE exclude regexp patterns listed in FILE --rinclude=PATTERN

Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

I've been having problems trying to sync two small partitions (128MB) that may be near to full. If rsync gets a write error (such as is caused when you fill up a partition) during a sync without the use of "-T", it will stop with this error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream

I've been studying the read and write buffering in rsync and it turns out most I/O is done just a couple of bytes at a time. This means there are lots of system calls, and also most network traffic comprises lots of small packets. The behavior is most extreme when sending/receiving file deltas of identical files. The main case where I/O is buffered is writes from the server (when io