search for: map_ptr

...urce and destination servers are running 2.5.2, I got the following error messages, can you please let me know what would be caused the errors? I copied back 2.3.2 version on both servers, and rsync went well. Thanks for the help, here is the errors: ch_what Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr collect_tests Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr Thanks, Jennifer

...ood reason to mandate it. Attached is a largish patch against rsync-2.5.5 that adds this feature. The primary issues are as follows: 1. Addition of a "--read-devices" option for activating the device reading behavior, and acting accordingly in a few locations. 2. The code and usage of map_ptr() required the file size to be known in advance. This is impossible for devices and FIFOs. To address this, I changed the interface of map_ptr. It now returns void rather than char*, and updates two new members of map_struct: - m_ptr contains the pointer to the new data - m_len contains the leng...

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

We're using rsync to mirror a web server. The rsync is initiated using ssh from a Red Hat Linux 7.2 box, the files are located on an Alpha running a version of Digital Unix 4. On the Alpha rsync is 2.5.2, The Linux box used to have a 2.4.6-X version, but with the map_ptr problems I built 2.5.2 on that as well. However, version incompatibility was not the problem, as they persist after the upgrade. The problems occur in a limited number of directories, and mostly with graphics files. The error message is "Warning:unexpected read size of 0 i map_ptr". Any...

...= map_file(fd, len, MAX_MAP_SIZE, CHUNK_SIZE); switch (checksum_type) { case CSUM_MD5: { @@ -302,8 +302,8 @@ void file_checksum(const char *fname, const STRUCT_STAT *st_p, char *sum) MD5_Init(&m5); - for (i = 0; i + CSUM_CHUNK <= len; i += CSUM_CHUNK) - MD5_Update(&m5, (uchar *)map_ptr(buf, i, CSUM_CHUNK), CSUM_CHUNK); + for (i = 0; i + CHUNK_SIZE <= len; i += CHUNK_SIZE) + MD5_Update(&m5, (uchar *)map_ptr(buf, i, CHUNK_SIZE), CHUNK_SIZE); remainder = (int32)(len - i); if (remainder > 0) @@ -319,8 +319,8 @@ void file_checksum(const char *fname, const STRUCT_STAT *s...

Hi list, Since upgrading rsync to version 2.5.2 on a Solaris 2.5.1 box, I see plenty of Warning: unexpected read size of 0 in map_ptr when doing my nightly backup (rsyncing some directories to an rsyncd on the same LAN). I have never seen this message before, and I only see it on the Solaris machine (I upgraded all my other machines to 2.5.2 as well). I hope this is not a FAQ... I did not find it mentioned recently. Thanks for...

https://bugzilla.samba.org/show_bug.cgi?id=1936 Summary: lseek failed in map_ptr Product: rsync Version: 2.6.3 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jitbose@yahoo.com QAContact...

Rsync has begun failing to replicate a kerberos samba mount point. This mount point has worked previously, but recently an attempt to replicate the mount point returns; lseek failed in map_ptr rsync error: error in file IO (code 11) at fileio.c(228) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(892) The only th...

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

Hi, When using rsync-3.0.2 through 3.0.5, I get this error on a large dataset syncing from machine-a to machine-b: $ /bin/rsync -aHSz /local/. machine-b:/local/. invalid len passed to map_ptr: -1737287498 rsync error: error in file IO (code 11) at fileio.c(188) [sender=3.0.5] This happens no matter which side initiates the connection, so this fails in the same way: $ /bin/rsync -aHSz machine-a:/local/. /local/. Using rsyncd, same thing so it's not caused by SSH: $ /bin/rsync -a...

...@@ -141,9 +141,9 @@ last_i = -1; if (verbose > 2) - rprintf(FINFO,"hash search b=%d len=%.0f\n",s->n,(double)len); + rprintf(FINFO,"hash search b=%lu len=%.0f\n",s->n,(double)len); - k = MIN(len, s->n); + k = MIN(len, (ssize_t)s->n); map = (schar *)map_ptr(buf,0,k); @@ -158,7 +158,7 @@ end = len + 1 - s->sums[s->count-1].len; if (verbose > 3) - rprintf(FINFO,"hash search s->n=%d len=%.0f count=%d\n", + rprintf(FINFO,"hash search s->n=%lu len=%.0f count=%lu\n", s->n,(double)len,s->count); d...

https://bugzilla.samba.org/show_bug.cgi?id=1936 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-02-27 14:14 ------- I've never been able to reproduce this bug. Are

...error: error in rsync protocol data stream (code 12) at io.c(600) [generator=3.0.5] -----8<----- After the last message I receive an alert from the MacOSX crash reporter about a access violation. I made the kernel dump it core and got the following backtrace: -----8<----- #0 0x0003123b in map_ptr (map=0x0, offset=0, len=32768) at fileio.c:192 192 if (offset >= map->p_offset && offset+len <= map->p_offset+map->p_len) (gdb) bt #0 0x0003123b in map_ptr (map=0x0, offset=0, len=32768) at fileio.c:192 #1 0x00011e54 in receive_data (f_in=5, fname_r=0x0, fd_r=-1...

https://bugzilla.samba.org/show_bug.cgi?id=8177 Summary: Problems with big sparsed files Product: rsync Version: 3.0.8 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: joluinfante at gmail.com

...rsync error: error in rsync protocol data stream (code 12) at token.c(288) "install-disk2.iso" is a CD-ROM image of "Turbo Linux Installer" and this CD-ROM includes many gzip/bzip2 compressed datas(RPMs). Let's looked at token.c. 280 tx_strm.next_in = (Bytef *) map_ptr(buf, offset, toklen); 281 tx_strm.avail_in = toklen; 282 tx_strm.next_out = (Bytef *) obuf; 283 tx_strm.avail_out = MAX_DATA_COUNT; 284 r = deflate(&tx_strm, Z_INSERT_ONLY); 285 if (r != Z_OK || tx_strm.avail_in != 0) { 286 rprintf(F...

In short: Platform: linux with 2.4 kernel Version: rsync 2.6.6 Command line: rsync266 -av -W --bwlimit=1 /mnt/somedir/rsync-2.6.6.tar.gz ./ Destination: local disk Source: file on a smbfs mounted filesystem; share is exported on a NT 4.0 workstation over a very slow and unstable link Result: Rsync completes operation with no special message, but the resulting file is damaged, large

...Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: an.m at outlook.com QAContact: rsync-qa at samba.org map_ptr() handles read failures by zeroing out remaining chunk and returning the partially filled/all zero buffers to callers. It also fills error details in map_struct->status. It is caller's responsibility to check the status and handle this condition appropriately. It is probably OK to ignore t...

...re1.tar.gz\* rsync 2.5.3 (not released yet) SECURITY FIXES: * Make sure that supplementary groups are removed from a server process after changing uid and gid. (Ethan Benson) BUG FIXES: * Fixed problem that in many cases caused the error message unexpected read size of 0 in map_ptr and resulted in the wrong data being copied. * Fixed compilation errors on some systems caused by the use of "unsigned int64" in rsync.h. * Fixed problem on systems such as Sunos4 that do not support realloc on a NULL pointer; error was "out of memory in f...

...,s->n,(double)s->flength); + sum.count,sum.remainder,sum.n,(double)sum.flength); - s->sums = (struct sum_buf *)malloc(sizeof(s->sums[0])*s->count); - if (!s->sums) out_of_memory("generate_sums"); - - for (i=0;i<count;i++) { - int n1 = MIN(len,n); - char *map = map_ptr(buf,offset,n1); + write_int(f_out, sum.count); + write_int(f_out, sum.n); + write_int(f_out, sum.remainder); - s->sums[i].sum1 = get_checksum1(map,n1); - get_checksum2(map,n1,s->sums[i].sum2); + for (i=0;i<sum.count;i++) { + int n1 = MIN(len,block_len); + char *map = map_ptr(buf,offs...

...ous mincore() hack. Here is my attempt at adding fadvise support to rsync (against v3.0.7). I do this in both the sender (hinting after match_sums()) and the receiver (hinting after receive_data()). In principle we could get better granularity if this was hooked up within match_sums() (or even the map_ptr() interface) and the receive loop in receive_data(), but I wanted to keep things simple at first (any comments on these ideas?) . At the moment is for little more than testing. Considering the potential negative effects of using FADV_DONTNEED on older kernels, it is likely we will want this functio...