similar to: Bug#624826: rsync: Bad interaction between -u and --partial

Hi, As the man page says, the --partial flag is to "keep partially transferred files". I'm assuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero

I've run into a bug in the IO handling when reading a file. Suppose I have a file that lives on an NFS filesystem. That filesystem is NOT being exported with auth=0 permissions. So, if I try to access a file as root, it successfully opens the file, but subsequent reads fail with EACCES. This produces a destination file full of null bytes. I noticed this with 2.5.7, but checked 2.6.2 as

Hi, One feature missing from rsync, and requested on this list before, is on-the-fly conversion of filename character encoding. For example, I often need to sync files having Hebrew filenames from a UTF-8 system (Linux) to an ISO8859-8 system (Cygwin on Windows 2000 using the non-Unicode Win32 interface). Other circumstances surely abound. Attached is a patch against rsync 2.6.2 that adds an

Hello, [ I've just reported this as https://bugzilla.samba.org/show_bug.cgi?id=2116 ] ------------------ rsync-2.6.3 can fail to report a write error. Here's a demonstration, writing to a full partition: You can reproduce it like this: $ echo foo > in $ strace -f -o log rsync in /full/tmp $ grep 'write.*ENOSP' log 4787 write(1, "foo\n", 4) =

https://bugzilla.samba.org/show_bug.cgi?id=2116 Summary: rsync ignores write error Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jim@meyering.net QAContact:

Hi, I have awaited the new release inorder to use the -"-partial-dir" option. But after testing it seems that it does not behave like it says on the tin. It will correctly move and rename the interrupted file to the declared directory, but it will not attempt to use it when the client attempts to rsync the file again. I have a Solaris 8 box running as a server (Matthew), and another

Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both

In the past there's been a need to provide consistency between symbolic links or repository metadata during a sync. Currently, rsync renames files piecemeal. The attached patch (extremely ugly) attempts to resolve this by foregoing the rename step until the end. It adds a new option (if we didn't, ls might catch up). There are several issues to get over. The first big one in

Hi, I have written a 'smallish' patch to implement the --inplace option as discussed on this mailing list at various points in the past. It makes a small modification to the sender algorithm so that it won't ask the receiver to relocate blocks from earlier in the file when running with the --inplace option. I would appreciate any testing and feedback people can provide! I

Hi There, This post is brought about due to the following two: http://www.mail-archive.com/rsync@lists.samba.org/msg10702.html http://www.mail-archive.com/rsync@lists.samba.org/msg10709.html I have a situation where I need to upload large files over an unstable link (resuming is a requirement) and only when they are complete can they be renamed and hence replace the original file. The

https://bugzilla.samba.org/show_bug.cgi?id=3718 Summary: RSync should verify permission/time before commiting a change Product: rsync Version: 2.6.5 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

We're using rsync to update the tables on our email relays, and very occasionally we get an error in the logs saying that a table has the wrong permissions. This is because of race conditions in finish_transfer() which mean that it does not update files atomically. This makes rsync not entirely safe to use in our situation, where the files being synced are frequently opened for short periods

The attached patch provides an additional check for the checksumming mode to ensure that a file that is actually written out to disk can be read back and has the same MD4 sum as the file on at the originating location. Regards, Nick. -------------- next part -------------- *** rsync-2.6.6pre1/receiver.c 2005-04-14 02:42:13.000000000 +0100 --- rsync-new/receiver.c 2005-07-26

Hi list, I couldn't find anything related to this, on mailing lists or even bugzilla, so here it is. A problem with this combination exists in the new 2.6.3 where the bwlimit code got rewritten and is not present at <= 2.6.2. The problem is that on io.c:882 bwlimit_writemax is also used to control the bandwidth, but it is not initialized for the daemon mode. At options.c:772 you can see

I am running RedHat 6.2 on many of my servers and am receiving the following errors when compiling Rsync 2.5.2: [root@wrapguy rsync-2.5.2]# make gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o In file included from rsync.c:23: rsync.h:339: warning: no semicolon at end of struct or union rsync.h:339: parse error before `inode' rsync.h:341: parse error before `dev'

I'm using rsync 2.6.9 and rsnapshot 1.2.9 on Ubuntu 8.04. When using rsnapshot to backup a remote computer over ssh, I get the message rsync error: unexplained error (code 130) at rsync.c(271) [generator=2.6.9] ERROR: /usr/bin/rsync returned 130 while processing root@undertow:/ I looked at the source for rsync 2.6.9, and line 271 in rsync.c is just a comment. Furthermore, it is in the

Hi, everyone~ I want to update rsynd from rsyncd-2.4.4. but I have a matter updating rsyncd-2.5.2 That is make failed. My server is based RedHat-7.0. My configure is successful because i saw message That is 'rsync 2.5.2 configuration successful." This is error messages. I want your advice about This problem. Thank you. ================================ cut [root@ux001 rsync-2.5.2]#

Hi, I've been experiencing this error for 2 weeks now. I don't now ehat could be a reason. I've tried to update with latest sources, but the same result (I'm not sure for line number, but the rest is the same). rsync: connection unexpectedly closed (5881604 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(359) My synchronized

Hi. I'm trying to compile rsync 2.6.0 on Solaris 9 Sparc, using gcc 3.2. The configure script seems to run with no problem. But when I go ahead to make, I get the following error output: -----8<------------------------------------------------------------ gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o In file included from rsync.c:23: rsync.h:371: warning: no semicolon

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