similar to: rsync 1tb+ each day

I have attached a patch that supports a new "--direct-write" option. The result of using this option is to write directly to the destination files, instead of a temporary file first. The reason this patch is needed is for rsyncing to a device where the device is full or nearly full. Say that I am writing to a device that has 1 Meg free, and a 2 meg file on that device is out of date.

While going through an old todo list I found that these patches had fallen by the way-side. About a year ago I initiated a discussion[1] with the Linux kernel folks regarding the lack of any useable fadvise support on the kernel side. As a result, I was observing extremely poor performance on my server after backup as executable pages were being swapped out in favor of data waiting to be flushed

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

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 List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

Hi! I am trying to do a IMHO rather trivial thing with rsync via ssh: I have some files under /etc and some under /home/thomas, I want to rsync just these to a remote PC with a similar setup where they should end up in the same dirs, and this with a single rsync call. Bascially 'tar --files-from FILE -cf - | netcat' and 'cd /; netcat | tar -xf -' with the optimisation rsync

Short question: is there way to tell EM to actually send data after send_data call? I''m building a file transferring app. I send Mashal.dump''ed metadata first, and then - the file contents (chunked). I found a silly bug: receive_data() gets marshalled metadata and the first chunk of the file in a single variable. Like that: c1.send_data("meta")

[I sent this the other day, but it never got approved for the list] I've been having problems trying to sync two small partitions (128MB) that are usually near being full. The rsync would fail with this cryptic error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) It ends up

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

Hi, i am using Rsync for making backups of a MySQL database. The MySQL files can be compressed about 1:10 and i want to make use of this fact. Rsync currently doesn't support saving files in a compressed state. I personally think this should be a feature for the filesystem (in the sense of "synchronised files") but currently there is no such filesystem for Linux available.

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

Hallo, I am using rsync to copy remote files into a local directory. I use the following flags: "--remove-sent-files --partial-dir=/tmp --partial --temp-dir=/tmp --backup --suffix=.bak". I need the partial issue since in the final destination I must have only closed and full files. I need to remove the sent files from the destination since I need to avoid transferring the same file

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

https://bugzilla.samba.org/show_bug.cgi?id=6293 Summary: rsync crashes when transferring files Product: rsync Version: 3.0.5 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: dirk.samba@miriup.de

https://bugzilla.samba.org/show_bug.cgi?id=5147 Summary: Read-only files that have changed xattrs fail to allow xattr changes Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >

https://bugzilla.samba.org/show_bug.cgi?id=4079 Summary: rsync fails with --inplace, --link-dest and --no-whole- file Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Warning for kernel folks: I'm not much of an mm person; let me know if I got anything horribly wrong. Many folks use rsync in their nightly backup jobs. In these applications, speed is of minimal concern and should be sacrificed in order to minimize the effect of rsync on the rest of the machine. When rsync is working on a large directory it can quickly fill the page cache with written data,

Hi, Running rsync with --whole-file yields poorer performance results than a simple "cp". Looking at the code - it looks like "copy_file" isn't really called when I add the --whole-file flag. The regular "receive_data" is doing the copy. Anyone encountered this? No other special flags (rsync --whole-file -av /mnt/ttt /home/sss/ ). Thanks, Amir --------------